Systems and methods for identifying parties based on coordinating identifiers

ABSTRACT

Systems and methods for allowing separate parties to identify each other through the use of matching computer-coordinated identifiers are discussed. In some cases, the methods include using a processor of a computer system to identify a first computer device configured to provide a first perceptible identifier, using the processor to identify a second computer device that is configured to provide a second perceptible identifier, and using the processor to send the first perceptible identifier to the first computer device and the second perceptible identifier to the second computer device, wherein the first and second perceptible identifiers correspond with each other to provide a two-sided, computer-coordinated verification. In some cases, the described methods include modifying the first and second identifiers as the first and second computer devices come into proximity with each other. Other implementations are discussed.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates to systems and methods for identifyingparties through the use of one or more corresponding,computer-coordinated identifiers. In particular, some implementations ofthe present invention relate to systems and methods for using a serveror other computer system to provide (wirelessly or otherwise)computer-coordinated perceptible identifiers (such as one or moreimages, light emissions, sounds, touch-perceptible notifications, and/orother suitable identifiers) to two or more computer devices, with theidentifiers received by each of the devices coordinating with each otherto allow users of such devices to readily match the identifiers and tothereby identify each other. In some implementations, the describedsystems and methods automatically ensure that coordinating identifiersreceived by computer devices participating in a first interaction do notcoordinate with an identifier provided to another device participatingin a second interaction when such other device is within a set proximityfrom one of more of the computer devices associated with the firstinteraction. Moreover, in some implementations, the coordinatingidentifiers received by one or more of the computer devicesparticipating in an interaction are configured to be modified when suchdevices come into proximity with each other.

2. Background and Related Art

Whether to meet a blind date met on a social media site, to grab acoffee from a busy café, to hail a taxi, to receive a pizza from a pizzadeliveryman, to pick up carryout from a restaurant, or for any other ofa wide variety of purposes, people regularly find themselves insituations where they need to be sure that the person they are meetingis actually the person they intended to meet.

Currently, people use an assortment of techniques to help ensure thatthey are meeting the right person. For instance, when a limo driver goesto the airport to pick up an unfamiliar passenger, the driver may holdup a sign displaying the passenger's name. In other instances, peoplemay agree to identify each other by meeting at a specific location(e.g., at a specific address, at a land mark, and/or in any othersuitable location). In still other instances, parties may agree to lookfor an identifying characteristic (e.g., a specific article of clothing,a license plate number, a car make and model, a physical characteristic,etc.) to identify each other. In yet other instances, one party may usea picture of another party (and/or of that other party's car or anotherobject) to identify that other party.

While there are many conventional techniques for identifying parties,such techniques are not necessarily without their shortcomings. Indeed,although some conventional techniques may help two or more parties tomeet each other, in many cases, as parties use such techniques they maystill question whether they are actually meeting the right person orsomeone else (e.g., an imposter, an opportunist, etc.). In one example,when a driver waits at an airport holding a sign for John Smith, and aman claims to be John Smith and even has a driver's licensecorroborating his claim, it may be hard for the driver to be certainthat he/she is meeting the intended John Smith.

In another example, when two parties agree to meet in a specificlocation, and multiple people end up being in that location at thescheduled meeting time, one or both of the two intended parties may(under some conventional techniques) have to approach and interact withmultiple people before being able to identify the other intended party.In yet another example, some parties may have a hard time identifyingeach other in the dark. For instance, if it is dark, it may be difficultfor one party to recognize a physical characteristic (e.g., hair color,clothing color, etc.), a license plate number, a car color, and/oranother characteristic of the other party—even if one or both of theparties have a photo of the other and/or of a car or other object orperson associated with the other party.

Indeed, not only can some conventional techniques for identifyingparties leave room for doubt as to whether the intended parties are theones actually meeting, be unnecessarily time consuming, and place one ormore individuals in an awkward situation, in some cases, conventionaltechniques for identifying parties, can allow one or more individuals toexpose themselves to danger by unintentionally believing that anotherparty is actually the intended party. This can be especially true whereone party is inviting another (e.g., a purported blind date, repairman,salesman, deliveryman, etc.) into a home, where one party is gettinginto a car with the other party, or where a person is otherwise trustinganother party with that person's safety.

Thus, while techniques currently exist that are used to identifydisparate parties, challenges still exist, including those discussedabove. Accordingly, it would be an improvement in the art to augment oreven replace current techniques with other techniques.

SUMMARY OF THE INVENTION

The present invention relates to systems and methods for identifyingparties through the use of one or more corresponding,computer-coordinated identifiers. In particular, some implementations ofthe present invention relate to systems and methods for using a serveror other computer system to provide (wirelessly or otherwise)computer-coordinated perceptible identifiers (such as one or moreimages, light emissions, sounds, touch-perceptible identifiers, and/orother suitable identifiers) to two or more computer devices, with theidentifiers received by each of the devices coordinating with each otherto allow users of such devices to readily match the identifiers and tothereby identify each other. In some implementations, the describedsystems and methods automatically ensure that coordinating identifiersreceived by computer devices participating in a first interaction do notcoordinate with an identifier provided to another device participatingin a second interaction when such other device is within a set proximityfrom one of more of the computer devices associated with the firstinteraction. Moreover, in some implementations, the coordinatingidentifiers received by one or more computer devices participating in aninteraction are configured to be modified when such devices come intoproximity with each other.

Some implementations of the present invention take place in associationwith a server, cloud, and/or other remote computer system and two ormore computer devices (e.g., wireless computer device, smart phones,laptops, etc.) that are configured to communicate with the remotecomputer system. In some cases, the methods include using a processor ofa computer system to identify a first computer device configured toprovide a first perceptible identifier; using the processor of thecomputer system to identify a second computer device that is configuredto provide a second perceptible identifier; and using the processor ofthe computer system to provide the first perceptible identifier to thefirst computer device and the second perceptible identifier to thesecond computer device, wherein the first and second perceptibleidentifiers correspond with each other to provide two-sided,computer-coordinated verification. In other words, some implementationsof the described systems and methods provide one or more parties withmatching identifiers, allowing such parties to readily and reliablyidentify each other.

Some implementations of the described invention further embrace acomputer program product for implementing within a computer system amethod for dynamically identifying parties through use of correspondingidentifiers in a manner that solves a technical problem ofmis-identifying parties due to a lack of a provision of party-specificinformation, the computer program product comprising: acomputer-readable, non-transitory medium for providing computer programcode means utilized to implement the method, wherein the computerprogram code means comprises executable code for implementing steps for:using a processor of a computer system to identify a first computerdevice configured to use a processor and a display of the first computerdevice to provide a first visually perceptible identifier; using theprocessor of the computer system to identify a second computer devicethat is configured to use a processor and display of the second computerdevice to provide a second visually perceptible identifier; using theprocessor of the computer system to provide the first visuallyperceptible identifier to the first computer device and the secondvisually perceptible identifier to the second computer device, whereinthe first and second visually perceptible identifiers correspond witheach other to provide a computer-coordinated verification for the firstcomputer device and the second computer device; and using the processorof the computer system to correlate a location of the first computerdevice with a location of the second computer device and toautomatically modify the first and second perceptible identifiers on thefirst and second computer devices when the first and second computerdevices are in proximity to each other.

Additionally, some implementations of the described invention include amethod for providing coordinating identifiers over a network to multipleremote computer devices, the method comprising: providing aparty-identification application for use on a first remote computerdevice and a second remote computer device; using a server to provide,via a network, a first identifier to the first computer device and asecond identifier to the second computer device, wherein the firstidentifier and the second identifier coordinate with each other, whereinthe server comprises a computer processor and a memory that storesinformation identifying the first identifier provided to the firstcomputer device and the second identifier provided to the secondcomputer device, and wherein the computer processor: determines alocation of at least one of the first computer device and the secondcomputer device; determines location of a third computer device; andensures that the first identifier and the second identifier do notcoordinate with a third identifier provided to the third computer devicethrough the server when the third computer device is in potentialproximity to the at least one of the first computer device and thesecond computer device.

In some further implementations, the described systems and methodsrelate to a method for providing coordinating identifiers over a networkto remote computer devices, the method comprising: providing aparty-identification application for use on a first remote computerdevice and a second remote computer device, the application providing aforum for placement of a request from a user of the first device; usinga server to place the first device and the second device in a firstinteraction with each other, to deliver at least a portion of therequest from the first device to the second device, to provide a firstidentifier to the first device, and to provide a second identifier tothe second device, wherein the first identifier and second identifiercoordinate with each other, wherein the server comprises a computerprocessor and a memory that stores information identifying the firstidentifier and the second identifier and wherein the computer processor:determines a location of a third-party computer device pertaining to athird-party interaction; determines a location of at least one of thefirst device and the second device; and automatically ensures that atleast one of the first identifier and the second identifier does notcoordinate with a third identifier that is assigned to a third-partyinteraction when the third-party device is within a set distance fromthe at least one of the first device and the second device.

In still other implementations, the described systems and methods relateto a method for providing coordinating identifiers over a network tomultiple remote computer devices, the method comprising: providing aparty-identification application for use on a first remote computerdevice, a second remote computer device, and a third remote computerdevice; using a server to link the first and second devices in a firstinteraction and to provide, via the network, a first set of coordinatingidentifiers to the first and second devices; using the server to linkthe second and third devices in a second interaction and to provide, viathe network, a second set of coordinating identifiers to the second andthird devices, wherein the server comprises a computer processor and amemory that stores information identifying the first and second sets ofidentifiers, and wherein the computer processor ensures that the firstand second sets of coordinating identifiers do not coordinate with eachother.

In yet other implementations, the described systems and methods relateto a method for providing coordinating identifiers over a network tomultiple remote computer devices, the method comprising: providing aparty-identification application for use on a first remote computerdevice, a second remote computer device, and a third remote computerdevice; using a server to link the first and second devices in a firstinteraction and to provide, via the network, a first set of coordinatingidentifiers to the first and second devices; using the server to linkthe second and third devices in a second interaction and to provide, viathe network, a second set of coordinating identifiers to the second andthird devices, wherein the server comprises a computer processor and amemory that stores information identifying the first and second sets ofidentifiers, wherein the computer processor ensures that the first andsecond sets of coordinating identifiers do not coordinate with eachother, and wherein at least one of the computer processor and aprocessor of the second device to cause the second device toautomatically display an identifier from the first set of identifierswhen the first device is closer to the second device than the thirddevice and to automatically display an identifier from the second set ofidentifiers when the third device is closer to the second device thanthe first device.

In still other implementations, the described systems and methods relateto a method for providing coordinating identifiers over a network tomultiple remote computer devices, the method comprising: providing aparty-identification application to a first computer device, a secondcomputer device, and a third computer device; using a processor of aserver to link the first, second, and third computer devices in a firstinteraction, using the processor to provide the first and second deviceswith a first set of coordinating identifiers; using the processor toprovide the second and third devices with a second set of coordinatingidentifiers; using the processor to determine a location of the first,second, and third devices; and using the processor to automaticallyensure that the first set of coordinating identifiers does notcoordinate with an identifier of a fourth device pertaining to a secondinteraction when the fourth device is in proximity with at least one ofthe first device and the second device.

In some implementations, the described systems and methods relate to amethod for providing coordinating identifiers over a network to multipleremote computer devices, the method comprising: providing aparty-identification application to a first computer device, a secondcomputer device, a third computer device, a fourth computer device, anda fifth computer device; using a processor of a server to link thefirst, second, and third devices in a first interaction and to providethe first, second, and third devices with a first set of coordinatingidentifiers; using the processor of a server to link the second, fourth,and firth devices in a second interaction and to provide the second,fourth, and fifth devices with a second set of coordinating identifiers;and using the processor to automatically ensure that the first andsecond sets of identifiers are distinguishable from each other.

In still some additional implementations, the described systems andmethods relate to a method for providing coordinating identifiers over anetwork to multiple remote computer devices, the method comprising:providing a party-identification application to a first computer device,a second computer device, and a third computer device; using a processorof a server to link the first, second, and third computer devices in afirst interaction and to provide the first, second, and third deviceswith a first set of coordinating identifiers; associating an identifiercoordinating with the first set of identifiers with an item to be passedfrom a user of the first device, to a user of the second device, and toa user of the third device; using the processor to determine a locationof the first, second, and third devices; and using the processor toautomatically ensure that the first set of coordinating identifiers doesnot coordinate with an identifier of a fourth device pertaining to asecond interaction when the fourth device is in proximity with at leastone of the first device and the second device.

In some implementations, the described systems and methods areconfigured to automatically modify (e.g., change, cause to flash, changeof speed of the flash, include a message, alternate between identifiers,and/or to otherwise modify) the first and/or second identifiers (and/orany other identifiers in an interaction) as the first and secondwireless computer devices (and/or other devices in the interaction) comeinto proximity with each other. In some implementations, the describedsystems allow users of one or more of the computer devices involved inan interaction to request that the first and/or second identifiers bedynamically modified to provide additional identity confirmation betweenthe users of the first and second computer devices. Indeed, in someimplementations, when a user of a first device requests for an updateand/or other modification to the identifier provided by the firstdevice, the coordinating identifiers displayed and/or otherwise providedby other devices in the same interaction as the first device are alsoupdated and/or modified in the same manner as is the identifier providedby the first device.

In some cases, the described systems and methods are further configuredto use the processor of the remote computer system (and/or a processorof one or more computer devices) to ensure that a computer device thatis not part of a specific interaction but that is in proximity toanother device that is part of the interaction does not have anidentifier that matches or otherwise coordinates with the identifierprovided to the device that is part of that specific interaction.Accordingly, in some implementations, the described systems and methodsare configured to prevent parties who are in proximity to each other,but who are not part of the same interaction, from receiving matchingidentifiers.

In some cases, the described systems and methods are configured to allowa user of one computer device to pass or otherwise send an identifierprovided on that user's device to another computer device. Accordingly,in some implementations, one person can pass their identifier to another(e.g., so as to replace the first person in an interaction) and/or oneperson can add another person to an interaction (e.g., so that the firstperson continues to be part of the interaction and one or more otherpeople are added to the interaction).

In some instances, the described systems and methods are configured totrack at least one of a time, path, distance, and/or other suitablecharacteristic that can be measured and/or otherwise recorded while twoor more computer devices comprising coordinating identifiers (e.g.,participating in the same interaction) are in proximity to (and/or outof proximity with) each other.

Although in some implementations, the described systems are configuredto provide a first identifier to a first computer device and a secondcoordinating identifier to a second device, in some otherimplementations, the described systems and methods include sendingcoordinating identifiers to virtually any number of computer devicesparticipating in one or more interactions. In one example, the describedsystems and methods send a first identifier to one person (e.g., apotential driver), while sending a second identifier, which coordinateswith the first) to multiple people (e.g., multiple passengers).

In some implementations, the described systems and methods allow atleast one of the remote computer system, a first computer device, asecond computer device, and/or any other suitable device to provide oneor more visual, audio, and/or touch-perceptible identifiers through anobject (e.g., a vehicle, watch, ear piece, headset, and/or any othersuitable device) that is in signal communication with at least one ofthe computer device in an interaction. Indeed, in some implementations,the remote computer system, a first computer device, and/or a secondcomputer device are configured to control a car's lights, horn,speakers, and/or other visual and/or audio outputs to help a potentialrider identify the car and driver.

In some implementations, the described systems and methods are furtherconfigured to use a camera on at least one computer device to identify aperson or object associated with another computer device pertaining tothe same interaction. While this can be accomplished in any suitablemanner, in some embodiments, the described systems and methods includethe use of facial, optical, and/or visual recognition technology.

In some implementations, the described systems and methods allow onecomputer device participating in multiple interactions to receivemultiple identifiers (e.g., with each identifier pertaining to adifferent interaction). In this regard, while a first computer devicecomprising multiple identifiers can function in any suitable manner, insome implementations, the described systems and methods are configuredto cause such a computer device to, by default, display and/or otherwiseprovide an identifier that coordinates with an identifier provided byanother computer device that is in an interaction with the first deviceand that is closer in proximity to the first device than any otherdevice that is in an interaction with the first device. In some suchimplementations, once one interaction is completed, the first computerdevice is configured to provide an identifier that coordinates with anidentifier of the next closest device that is in an interaction with thefirst device.

In some further implementations, the described systems and methods areconfigured to provide information, reading material, promotionalmaterials, advertisements, pop-up ads, factual information, touristinformation, notifications, coupons, and/or any other suitable materialthrough computer devices functioning in accordance with the describedsystems and methods. Indeed, in some implementations, the describedsystems and methods provide advertising materials to one or morecomputer devices in an interaction in connection with one or morecoordinating identifiers. Accordingly, in some such implementations, thedescribed systems and methods are configured to generate revenue throughadvertising.

In yet other implementations, the described systems and methods areconfigured to allow an identifier to be used in place of a ticket (e.g.,for entry to a movie, concert, game, play, meeting, meal, and/or otherevent). In some such implementations, the identifier (or ticket)assigned to a first computer device can be reassigned from the firstcomputer device to any other suitable number of computer devices, suchthat the identifier (or ticket) could be “passed on”.

While the methods and processes described herein can be particularlyuseful in the areas of transportation (e.g., allowing one or moredrivers and one or more potential passengers to identify each other),courier services (e.g., allowing one or more senders and/or recipientsto identify one or more couriers), event ticketing (e.g., where anidentifier functions as one or more tickets), concessions (e.g.,allowing one or more concession workers and one or more patrons torecognize each other), and queue management (e.g., alerting a party toan interaction when that parties turn has arrived and using acoordinating identifier to show that the turn has indeed arrived), thoseskilled in the art can appreciate that the described methods andprocesses can be used in a variety of different applications and in avariety of different areas of manufacture to help parties readilyidentify each other and/or for a number of other purposes.

By way of non-limiting example, some implementations of the describedsystems and methods can be used to help individuals identify and verifyeach other for home deliveries, dating (e.g., for blind dates, datesarranged through a website and/or dating app, etc.), classified addpurchases (e.g., as users of Craig's List, Angie's List, the newspaper,and/or any other suitable forum to make a purchase, close a deal, and/orto provide/receive services), as parties meet to broker ticket sales(e.g., ticket resale brokering), airport pick up, appointments (e.g.,with salesmen, repairmen, missionaries, recruiters, service providers,etc.), breaking groups of people into smaller groups, food delivery,and/or any other suitable circumstance in which at least one party wantsto identify another party and/or location.

These and other features and advantages of the present invention will beset forth or will become more fully apparent in the description thatfollows and in the appended claims. The features and advantages may berealized and obtained by means of the instruments and combinationsparticularly pointed out in the appended claims. Furthermore, thefeatures and advantages of the invention may be learned by the practiceof the invention or will be obvious from the description, as set forthhereinafter.

BRIEF DESCRIPTION OF THE DRAWINGS

In order that the manner in which the above recited and other featuresand advantages of the present invention are obtained, a more particulardescription of the invention will be rendered by reference to specificembodiments thereof, which are illustrated in the appended drawings.Understanding that the drawings depict only typical embodiments of thepresent invention and are not, therefore, to be considered as limitingthe scope of the invention, the present invention will be described andexplained with additional specificity and detail through the use of theaccompanying drawings in which:

FIGS. 1A-1B illustrate face views of two separate wireless computerdevices displaying coordinating identifiers in accordance with someembodiments of the described systems and methods;

FIGS. 1C-1D illustrate face views of two separate computer devicesdisplaying coordinating identifiers in accordance with some embodiments;

FIG. 2A illustrates a representative system that provides a suitableoperating environment for use with some embodiments of the describedsystems and methods;

FIGS. 2B-3 each illustrate a representative networked environment foruse with some embodiments of the described systems and methods;

FIG. 4 illustrates a server-centric flowchart showing a representativeembodiment of a method for identifying parties by providing such partieswith coordinating identifiers;

FIG. 5 illustrates a client- (or computer device) centric flowchartshowing a representative embodiment of a method for identifying partiesby providing such parties with coordinating identifiers;

FIG. 6 illustrates a flowchart depicting a representative embodiment ofa method for modifying coordinating identifiers based on proximity ofone or more computer devices in a transaction;

FIG. 7 illustrates a flowchart depicting a representative embodiment ofa method for preventing a coordinating identifier from a firsttransaction from being the same as a coordinating identifier from asecond transaction when a computer device from the first transaction isin proximity to a computer device from the second transaction;

FIG. 8 illustrates a flowchart depicting a representative embodiment ofa method for displaying a coordinating identifier on a computer devicethat is participating in multiple transactions;

FIG. 9 illustrates a feature of some embodiments of the invention inwhich a coordinating identifier is made available to computer devices ina first radius, is not made available to computer devices that areoutside the first radius but that are inside a second radius, and ismade available outside the second radius;

FIG. 10 illustrates a flowchart depicting a representative embodiment ofa method for using coordinating identifiers to help a potential driverand one or more intended passengers to identify each other;

FIG. 11 illustrates a flowchart depicting a representative embodiment ofa first method for using the described systems and methods in a courierservice;

FIG. 12A illustrates a diagram showing a representative embodiment of amethod for using the described systems and methods in the courierservice;

FIG. 12B illustrates a flowchart depicting a representative embodimentof a second method for using the described systems and methods in acourier service;

FIG. 13 illustrates a flowchart depicting a representative embodiment ofa method for using the described systems and methods for ticket sales;

FIG. 14A illustrates a flowchart depicting a representative embodimentof a method for using the described systems and methods to purchaseconcession items;

FIG. 14B illustrates a diagram in which computer devices for one serverand multiple patrons provide belong to one transaction and sharecoordinating identifiers;

FIG. 14C illustrates a diagram in which computer devices for one patronand multiple servers provide belong to one transaction and sharecoordinating identifiers; and

FIG. 15 illustrates a flowchart depicting a representative embodiment ofa method for using the described systems and methods to manage one ormore queues.

DETAILED DESCRIPTION OF THE INVENTION

Reference throughout this specification to “one embodiment,” “anembodiment,” “an implementation,” or similar language means that aparticular feature, structure, or characteristic described in connectionwith the embodiment or implementation is included in at least oneembodiment of the present invention. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” “in another embodiment,” “insome implementations,” “in some other embodiments,” “in some otherimplementations,” and similar language throughout this specificationmay, but do not necessarily, all refer to the same embodiment.

Furthermore, the described features, structures, or characteristics ofthe described systems and methods may be combined in any suitable mannerin one or more embodiments. In the following description, numerousspecific details are provided, such as examples of suitable computerdevices, computer systems, methods for identifying parties, methods forlocating computer devices, etc., to provide a thorough understanding ofembodiments of the invention. One having ordinary skill in the relevantart will recognize, however, that the described systems and methods maybe practiced without one or more of the specific details, or with othersystems, methods, techniques, components, materials, and so forth. Inother instances, well-known systems, structures, materials, methods, oroperations are not shown or described in detail to avoid obscuringaspects of the invention.

The present invention relates to systems and methods for identifyingparties through the use of one or more corresponding,computer-coordinated identifiers. In particular, some embodiments of thepresent invention relate to systems and methods for using a server orother computer system to provide (wirelessly or otherwise)computer-coordinated perceptible identifiers (such as one or moreimages, light emissions, sounds, touch-perceptible identifiers, and/orother suitable identifiers) to two or more computer devices, with theidentifiers received by each of the devices coordinating with each otherto allow users of such devices to readily match the identifiers and tothereby identify each other. In some embodiments, the described systemsand methods automatically ensure that coordinating identifiers receivedby computer devices participating in a first transaction do notcoordinate with an identifier provided to another device participatingin a second transaction when such other device is within a set proximityfrom one of more of the computer devices associated with the firsttransaction. Moreover, in some embodiments, the coordinating identifiersreceived by one or more of the computer devices participating in atransaction are configured to be modified when such devices come intoproximity with each other and/or as otherwise desirable.

In the disclosure and in the claims the term identifier; identifiers;computer-coordinated identifier; corresponding, computer-coordinatedidentifier; perceptible identifier; matching identifier; and variationsthereof may refer to one or more: visually perceptible symbols, shapes,patterns, images, icons, objects, drawings, photos, marks, words,letters, numbers, colors, color schemes, logos, trademarks, servicemarks, flashes, alternating colors, codes, advertisements, videos,audio/visual works, light emissions, combinations of the foregoing(e.g., multiple identifiers shown together; alternating colors, images,symbols, etc.; and/or any other suitable combination), and/or othervisible material that can be shown on an electronic display or from anoutput that is in signal communication with an electronic device;audibly perceptible sounds, buzzes, beeps, ring tones, types of music,songs, words, statements, noises, patterns, combinations of theforegoing, and/or other audible sounds that can be produced by acomputer device and/or an output that is in signal communication withthe computer device; touch perceptible vibrations, forces, contacts,tactile notifications, cutaneous notifications, kinestheticnotifications, haptic notifications, combinations of the foregoing,and/or other touch perceptible actions that can be produced by acomputer device and/or an output that is in signal communication withthe computer device; other forms of stimulus that can be produced by acomputer device and/or an output that is in signal communication withsuch device (and/or a server or other computer system); and/orcombinations of the foregoing.

In some embodiments, the identifiers in an interaction or a transactioncomprise a visually perceptible display (e.g., shown on the computerdevices in the transaction) that match or otherwise coordinate with theother identifiers provided by the other computer devices in thetransaction. Accordingly, in some such embodiments, parties can show theidentifiers on their computer devices to each other to readily determinewhether or not the other parties are part of the same transaction. Byway of non-limiting illustration, FIGS. 1A-1D show some representativeembodiments in which the identifiers 10 and 12 each comprises an imagedisplaying a shape 12 (e.g., one or more stars, circles, triangles,squares, rectangles, octagons, polygons, irregular shapes, regularshapes, symmetrical shapes, asymmetrical shapes, character, mascot,symbol, one or more portions of a shape, a part of a puzzle, and/or anyother suitable shape, portion of a shape, object, image, and/or lighte-mission) with any suitable color scheme.

As used herein, the terms coordinate, coordinating, correspond,corresponding, match, and variations thereof may refer to a relationbetween two or more identifiers that allow such identifiers to: beexactly the same; be very similar to each other; be as close to the sameas possible, accounting for variations in the functionality of thedevices displaying and/or otherwise providing the identifiers; exactlymatch each other; substantially match each other; be mirror images ofeach other; be a positive and a negative image of each other; create afull image, word (e.g., “SHER” and “LOCK”), number, symbol, picture,image, and/or other identifier when used together; fit together (e.g.,as portions of the same image, as puzzle pieces, a parts of the samesong and/or sound, as matching images to be shown together, ascoordinating images to be shown together, as different parts of the samesong, and/or in any other suitable manner); complement each other (e.g.,by having different identifiers that complement each other, such as byhaving one device display an image of a basketball and another devicedisplaying an image of a basketball hoop (possibly with both imagesbeing shown together when the devices come into proximity with eachother and/or at any other suitable time) and/or any other suitablecomplementary identifiers; have a sound and/or vibration thatcorresponds to a visual identifier (e.g., having one identifier comprisean audible version of a song, such as Jingle Bells, with the anothercoordinating identifier comprising an image corresponding to the song,such as an image of a jingle bell); having matching images that flash atthe same and/or different times; and/or otherwise be readilyidentifiable as corresponding to (or otherwise matching) each other.Indeed, in some embodiments, coordinating identifiers comprise imagesthat are substantially similar, if not exactly similar, to each other.By way of non-limiting illustration, FIGS. 1A and 1B show someembodiments in which two separate wireless computer devices 14 and 16each show coordinating identifiers 10 that are readily matched with eachother, and distinguished from other identifiers (e.g., those identifiersshown on the computer devices 18 and 20 of FIGS. 1C and 1D).

As used herein, the terms interaction, interactions, transaction,transactions, and variations thereof may, in some cases, be usedinterchangeably, and may refer to a session, communication, process,and/or other interaction between a remote computer system (e.g., aserver or other computer system) and/or two or more computer devices(e.g., desktop computers; wireless computer devices, such as phones,tablets, laptops, etc.; and/or other suitable computer devices), whereinas part of the transaction the two or more computer devices each receiveone or more identifiers that coordinate with each other (e.g., such thatparties associated with the computer devices can compare identifiers andreadily identify each other (e.g., as being part of the sametransaction)).

The following disclosure of the described systems and methods is groupedinto two subheadings, namely “Representative Operating Environment” and“Methods.” Utilization of the subheadings is for convenience of thereader only and is not to be construed as limiting in any sense.

Representative Operating Environment

The described systems and methods can be used with any suitableoperating environment and/or software. In this regard, FIG. 2A and thecorresponding discussion are intended to provide a general descriptionof a suitable operating environment in accordance with some embodimentsof the described systems and methods. As will be further discussedbelow, some embodiments embrace the use of one or more processing unitsin a variety of customizable enterprise configurations, including in anetworked or combination configuration, which may also include acloud-based service, such as a platform as a service, software as aservice, and/or as any other suitable service.

Some embodiments of the described systems and methods embrace one ormore computer readable media, wherein each medium may be configured toinclude or includes thereon data (non-transitory or transitory) orcomputer executable instructions for manipulating data. The computerexecutable instructions include data structures, objects, programs,routines, and/or other program modules that may be accessed by one ormore processors, such as one associated with a general-purpose modularprocessing unit capable of performing various different functions and/orone associated with a special-purpose modular processing unit capable ofperforming a limited number of, and/or specific, functions.

Computer executable instructions cause the one or more processors of theone or more enterprises to perform a particular function or group offunctions and are examples of program code means for implementing stepsfor methods of processing. Furthermore, a particular sequence of theexecutable instructions provides an example of corresponding acts thatmay be used to implement such steps.

Examples of computer readable media (including, without limitation,non-transitory computer readable media) include random-access memory(“RAM”), read-only memory (“ROM”), programmable read-only memory(“PROM”), erasable programmable read-only memory (“EPROM”), electricallyerasable programmable read-only memory (“EEPROM”), compact diskread-only memory (“CD-ROM”), any solid state storage device (e.g., flashmemory, smart media, etc.), and/or any other device or component that iscapable of providing data and/or executable instructions that may beaccessed by a processing unit.

With reference to FIG. 2A, a representative enterprise includes modularprocessing unit 200 (e.g., a computer system, a wireless computerdevice, and/or other computer device), which may be used as ageneral-purpose or a special-purpose processing unit. For example,modular processing unit (or computer device) 200 may be employed aloneor with one or more similar modular processing units as a smart phone, acellular phone, a feature phone, a tablet computer, a smart television,a mobile computer device, a personal computer, a notebook computer, aPDA or other hand-held device, a workstation, a minicomputer, amainframe, a supercomputer, a multi-processor system, a networkcomputer, a processor-based consumer device, a smart appliance ordevice, a control system, and/or the like. Indeed, in some embodiments,the modular processing unit comprises at least one of a server and acomputer device (including, without limitation, a wireless computerdevice). Using multiple processing units in the same enterprise providesincreased processing capabilities. For example, each processing unit ofan enterprise can be dedicated to a particular task or can jointlyparticipate in distributed processing.

In FIG. 2A, the modular processing unit 200 (e.g., a computer systemand/or computer device) includes one or more buses and/or interconnects205, which may be configured to connect various components thereof andenables data to be exchanged between two or more components. Thebus(es)/interconnect(s) 205 may include one of a variety of busstructures, including, without limitation, a memory bus, a peripheralbus, and/or a local bus that uses any of a variety of bus architectures.Typical components connected by the bus(es)/interconnect(s) 205 includeone or more processors 210 and one or more memories 220. Some othernon-limiting components that may be selectively connected to thebus(es)/interconnect(s) 205 through the use of logic, one or moresystems, and one or more subsystems, include one or more mass storagedevice interfaces 230, input interfaces 240, output interfaces 250,and/or network interfaces 260, each of which will be discussed below.

In some embodiments, the processing system 210 includes one or moreprocessors, such as a central processor, a microprocessor, andoptionally one or more other processors designed to perform a particularfunction or task. It is typically the processing system 210 (alsoreferred to as a processor or computer processor) that executes theinstructions provided on computer readable media, such as on the memory220, a magnetic hard disk, a removable magnetic disk, a magneticcassette, an optical disk, and/or from a communication connection, whichmay also be viewed as a computer readable medium.

In accordance with some embodiments, the memory 220 includes one or morecomputer readable media (including, without limitation, non-transitorycomputer readable media) that may be configured to include or includesthereon data or instructions for manipulating data, and may be accessedby the processing system 210 through the system bus 205. The memory 220may include, for example, ROM 222 used to permanently store information,and/or RAM 224 used to temporarily store information. In someembodiments, ROM 222 includes a basic input/output system (“BIOS”)having one or more routines that are used to establish communication,such as during start-up of computer device 200. In some embodiments, RAM224 includes one or more program modules, such as one or more operatingsystems, application programs, and/or program data.

One or more mass storage device interfaces 230 may be used to connectone or more mass storage devices 232 to the system bus 205. The massstorage devices 232 may be incorporated into and/or may be peripheral tothe computer device 200 and allow the computer device (and/or computersystem) 200 to retain large amounts of data. Optionally, one or more ofthe mass storage devices 232 may be removable from computer device 200.Examples of mass storage devices include hard disk drives, magnetic diskdrives, tape drives, solid state mass storage, and/or optical diskdrives.

Some non-limiting examples of solid state mass storage include flashcards and memory sticks. The mass storage device 232 may read fromand/or write to a magnetic hard disk, a removable magnetic disk, amagnetic cassette, an optical disk, or another computer readable medium.The mass storage devices 232 and their corresponding computer readablemedia provide nonvolatile storage of data and/or executable instructionsthat may include one or more program modules, such as an operatingsystem, one or more application programs (or applications), otherprogram modules, or program data. Such executable instructions areexamples of program code means for implementing steps for methodsdisclosed herein.

One or more input interfaces 240 may be employed to enable a user toenter data (e.g., initial information) and/or instructions to computerdevice (or computer system) 200 through one or more corresponding inputdevices 242. Examples of such input devices include a keyboard and/oralternate input devices, such as a digital camera, a sensor, bar codescanner, debit/credit card reader, signature and/or writing capturedevice, pin pad, touch screen, mouse, trackball, light pen, stylus orother pointing device, a microphone, a joystick, a game pad, a scanner,a camcorder, and/or other input devices. Similarly, examples of inputinterfaces 240 that may be used to connect the input devices 242 to thesystem bus 205 include a serial port, a parallel port, a game port, auniversal serial bus (“USB”), a firewire (IEEE 1394), a wirelessreceiver, a video adapter, an audio adapter, a parallel port, a wirelesstransmitter, and/or another interface.

One or more output interfaces 250 may be employed to connect one or morecorresponding output devices 252 to the system bus 205. Examples ofoutput devices include one or more monitors, projectors, displayscreens, speakers, lights, wireless transmitters, printers, and thelike. A particular output device 252 may be integrated with orperipheral to computer device 200. Examples of output interfaces includea video adapter, an audio adapter, a parallel port, and the like.

One or more network interfaces 260 enable computer device (or computersystem) 200 to exchange information with one or more local or remotecomputer devices, illustrated as computer devices 262, via a network 264that may include one or more hardwired and/or wireless links. Examplesof the network interfaces include a network adapter for connection to alocal area network (“LAN”) or a modem, a wireless link, an infraredlink, a BLUETOOTH® link, and/or another adapter for connection to a widearea network (“WAN”), such as the Internet. The network interface 260may be incorporated with or be peripheral to computer device 200.

In a networked system, accessible program modules or portions thereofmay be stored in a remote memory storage device. Furthermore, in anetworked system computer device 200 may participate in a distributedcomputing environment, where functions or tasks are performed by aplurality networked computer devices. While those skilled in the artwill appreciate that the described systems and methods may be practicedin networked computing environments with many types of computer systemconfigurations, FIG. 2B represents an embodiment of a portion of thedescribed systems in a networked environment that includes clients (orcomputer devices 265, 270, 275, etc.) and/or and one or more peripheraldevices (illustrated as multifunctional peripheral (MFP) MFP 280)connected to a server 285 via a network 260. While FIG. 2B illustratesan embodiment that includes three clients (e.g., computer devices, suchas smart phones and/or other wireless computing devices) connected tothe network (and one or more servers 285), alternative embodimentsinclude at least one client connected to a network or many (e.g., 2, 4,5, 6, 7, 8, and or any other suitable number of) clients connected to anetwork and/or one or more servers.

In one non-limiting illustration of a basic view of the describedsystems, FIG. 3 shows that, in some embodiments, the system comprisestwo or more computer devices (e.g., 365 and 375) that are connected to aserver (or other computer system) 385 through a network (e.g., theInternet and/or any other suitable server). While the computer devicescan comprise any suitable computer device (e.g., as described above),including, without limitation, a display comprising (or otherwise insignal communication with a device comprising a) processing unit (e.g.,a smart display, a smart TV, etc.), a smart phone, a cell phone, atablet, a laptop, a desktop computer, and/or any other suitable computerdevice, in some embodiments, the first computer device comprises a smartphone and the second computer device comprises smart phone and/or asmart display. In some other embodiments, however, at least one computerdevice (e.g., a first computer device 365) in a transaction comprises awireless computer device (e.g., a smart phone, cell phone, tablet,laptop, etc.) while at least one other computer device in thetransaction (e.g., a second computer device 375) comprises a computerdevice that is in signal communication with a display (e.g., TV,monitor, projector, screen, and/or other display).

Methods

While the described systems and methods can be implemented in anysuitable manner, FIGS. 4 and 5 show some non-limiting examples ofsuitable methods for using computer-coordinated identifiers to identifyseparate parties. In particular, FIG. 4 illustrates a representativemethod for helping two or more parties to identify each other, from theprospective of a server (or other computer system), while FIG. 5illustrates a representative method for helping two or more parties toidentify each other, from the prospective of one or more of the parties(e.g., via the parties' respective computer devices). In this regard, itshould be noted that each of these methods (as well as all other methodsdescribed herein) can be modified in any suitable manner. For instance,any suitable step can be added to, be removed from, be modified, bereordered within, and any additional step can be added to, each of thedescribed methods. It should also be noted, that while the term step isused herein, that term may be used to simply draw attention to differentportions of the described methods and is not meant to delineate astarting point or a stopping point for any portion of the methods, or tobe limiting in any other way.

With reference now to FIG. 4, that figure shows that, in someembodiments, the method 400 begins at steps 402 and 404 by identifyingtwo or more parties that are using the described systems and methods tomeet and identify each other. In this regard, a computer system (e.g.,server 385) and/or one or more parties can select and/or otherwiseidentify the various parties to a transaction in any suitable manner,including, without limitation, by providing an application (e.g., amobile app, a website, an online app, a software application, etc.) thatprovides the described systems and methods and allows one or moreparties to use such application to enter into a transaction with one ormore parties; by allowing one party to a transaction to select aspecific party for participation in that transaction, by determining whois logged into the system, by determining who has made a request and whocan fill the request, by determining who has made an offer and who iswilling to accept the offer, by determining who (or whose phone or othercomputer device) is in the closest proximity to a particular person (orthat person's phone or computer device), and/or in any other suitablemanner.

In one non-limiting example, a first party uses his or her computerdevice (e.g., a wireless device and/or otherwise) to access anapplication that functions in accordance with at least some embodimentsof the described systems and methods. In this example, the first partyis able to use the application (and/or any other suitable means ofcommunication, including, without limitation, a phone, fax, email, etc.)to request a good or service (e.g., a car ride), and another party isable (e.g., through use of the application and/or any other suitablecommunication channel) to use his or her computer device to indicatethat he or she can provide the requested good or service to the firstparty (e.g., that he or she is willing to provide a car ride).Additionally, in this example, the computer system (e.g., server 385),one of the two computer devices, and/or any other suitable systemdetermines, logs, and/or otherwise records that the first and the secondparty are part of the same transaction.

In accordance with some embodiments, FIG. 4 shows at step 406 thedescribed method involves determining whether the described systems willconduct one or more additional optional steps (as discussed below)before proceeding. If the system recognizes that one or more optionalsteps will be completed, FIG. 4 shows the optional step is completed atstep 408, and the described systems determine whether any additionaloptional steps will be completed (e.g., as shown at step 410. Once thedescribed systems have determined that no optional steps will becompleted at this time (and/or that all optional steps have beencompleted), FIG. 4 shows that the method 400 includes a step fordetermining (e.g., at step 412) whether or not an additional party is tobe added to the transaction.

In this regard, while steps 402 and 404 of FIG. 4 shows some embodimentsin which the described method 400 helps two parties to identify eachother, step 412 in that figure shows that, in some embodiments, thedescribed systems check, are told, and/or otherwise determine whetherany additional parties are to be part of the transaction. For instance,the described systems may check to see whether multiple people want toshare (or receive) a car ride (or other good or service).

If the system determines at step 412 that one or more additional parties(e.g., computer devices 365, 375, etc.) are to be involved in thetransaction, the system identifies (e.g., as shown at step 414) theadditional party (and/or the additional party's smart phone or othersuitable computer device) and logs that party (and/or the correspondingcomputer device) as being part of the transaction.

In some embodiments, once the system (e.g., the server 385 and/or one ormore computer devices 365, 375, etc.) determines that two or moreparties (or computer devices) will be part of a transaction (e.g., bydetermining at 412 that no (or one or more) additional parties willparticipate in the transaction), FIG. 4, at step 416, shows that, insome embodiments, the method 400 continues as the computer system (e.g.,server 385) (and/or any other suitable computer device) provides thefirst computer device 365, the second computer device 375, and/or anyother suitable computer device participating in the transaction withcoordinating identifiers.

In this regard, the computer system (e.g., server 385) and/or any othersuitable computer device can provide the first and second (and/or anyother) computer devices in the same transaction with coordinatingidentifiers in any suitable manner. Indeed, in some embodiments, oneparty is allowed to select an identifier and the system provides thatidentifier (and/or one or more other coordinating identifiers) to theother party or parties in the transaction. In another example, thesystem is told which identifier to use, and/or otherwise selects anidentifier and sends that identifier and/or another coordinatingidentifier (and/or a code, number, signal, and/or other informationindicating which identifier to produce) to the applicable computerdevice and/or devices.

FIG. 4 shows that, in some embodiments, the method 400 continues at step418 (much as shown at step 406) where the described systems (and/or oneor more users) determine whether the system will conduct one or moreadditional steps (as discussed below). If the system recognizes that oneor more optional steps will be completed, FIG. 4 shows the optional stepis completed at step 420, and the systems determine whether anyadditional optional steps will be completed (e.g., as shown at step422). Once the systems have determined that no optional steps will becompleted (or that all optional steps have been completed), FIG. 4 showsthat the computer system determines (e.g., at step 424) whether or notthe transaction is complete. In some embodiments, if the transaction isnot complete, the system returns to step 412 in the method 400 andcontinues on until it is complete. That said, if the system determinesthat the transaction is complete (e.g., the applicable parties haveidentified each other and/or a portion of the transaction is otherwisecompleted), FIG. 4 shows the method ends (e.g., at step 426), such thatthe method can be repeated.

Where the described systems (e.g., the computer system or server 385;one or more computer devices 365, 375, etc.; and/or any other suitableportion of the overall described system) determine that a transaction iscomplete and that the intended parties have properly identified eachother, the described systems can make that determination in any suitablemanner. By way of non-limiting example, some embodiments of thedescribed systems and methods determine that a transaction is completewhen one or more users of the computer devices that provide thecoordinating identifiers (e.g., the first device 365 and/or the seconddevice 375) in a transaction indicates that the transaction is cancelledor otherwise complete (e.g., by such user tapping the identifier onhis/her computer device (e.g., on a device with a touch screen), byproviding a command to terminate the transaction, by closing of an appand/or website used to initiate the transaction, by providing asignature (e.g., via a touch screen and/or other input), by turning offof one or more computer devices in the transaction, by sending a text,by sending an e-mail, and/or in any other suitable manner).

In another example, the described systems and methods are configured todetermine that a transaction (or at least a portion of a transaction) iscomplete when one or more barcodes, QR codes, RF signals, near fieldcommunication signals, infrared signals, BLUETOOTH® signals, radiosignals, and/or other information provided by one or more (e.g., all) ofthe devices (e.g., device 365, 375, etc.) in the transaction areregistered (e.g., scanned, picked up, received, etc.) by one or more(e.g., all) of the other devices in the transaction.

In still another example, the described systems and methods determinethat a transaction is complete when the computer devices (e.g., devices365, 375, etc.) that are identified as being part of a transaction aredetermined (e.g., via the GPS coordinates of the devices,multilateration of the devices, localization of the devices, informationprovided by one or more users of the devices (e.g., a current address,location, and/or other suitable information), and/or any other suitablemethod) to be within any suitable set distance from each other (e.g.,for any suitable time).

In yet another example, the described systems and methods are configuredto determine that a transaction is complete and/or reached a certainpoint when a camera, sensor, and/or software operating on or through oneor more (e.g., all) of the devices identified as pertaining to atransaction recognizes and/or otherwise identifies (via facialrecognition, object recognition, scanning, near field communications, IRcommunications, and/or otherwise) a face, car, license plate, code,sound, signal, and/or other object and/or identifier that is enteredinto the system as pertaining to one of the other parties in thetransaction.

In one non-limiting example, one or more devices in a transactionprovides one or more QR codes, bar codes, numeric codes, sounds,markings, codes, IR signals, BLUETOOTH® signals, near field signals,and/or any other suitable and recognizable marking and/or otheridentifier. In some such cases, as two or more devices in a transactioncome near each other (e.g., screen to screen and/or otherwise), one ormore of the devices can scan the other device (e.g., via a camera,scanner, IR receiver, BLUETOOTH® receiver, Wi-Fi receiver, near fieldreceiver, sensor, and/or in any other suitable manner) to recognizewhether or not that device comprises a marking or other identifiershowing that such device pertains to the desired transaction. In someinstances, when one or more devices in a transaction identify anotherdevice (and/or a person and/or other object associated with such device)in the transaction, one or more such devices modify their coordinatingidentifiers (e.g., by making a noise, playing a song, modifying one ormore images on the devices, posting a message, flashing, and/or in anyother suitable manner).

Accordingly, in some embodiments, in addition to (and/or in place of)recognizing parties by having users match coordinating identifiers, insome embodiments, the described systems and methods are configured tohave one or more computer devices in a transaction determine that theproper parties have met. Similarly, in some embodiments, when one ormore devices determines that another device (and/or person and/orobject) is not part of a transaction (e.g., via scanning, receiving asignal, comparing identifiers, optical recognition, and/or in any othersuitable manner), such devices may alert their users of the finding(e.g., by making a noise, providing a message, and/or in any othersuitable manner).

In still another non-limiting example, some embodiments of the describedsystems and methods determine that a transaction is complete when one ormore computer devices (e.g., 365, 375, etc.) identified in a transactionreceives a signature, fingerprint, retinal scan, biometric scan, and/orother similar indicator from one or more other parties to thetransaction.

Turning now to FIG. 5, that figure (as mentioned above) shows arepresentative embodiment similar to the method 400 of FIG. 4, but shownfrom the perspective of a party (e.g., the party's computer device) to atransaction. In particular, that figure shows that, in accordance withsome embodiments, the method 500 (or a transaction) begins at step 502as a first computer device 365 (e.g., a laptop, wireless phone, tablet,etc.) makes a connection with the server 385. This connection can bemade in any suitable manner, including, without limitation, by: logginginto an account, setting up an account, opening an app (e.g., a mobileapp, an online app, a website, one or more pieces of applicationsoftware, and/or any other suitable application) that accesses theserver, turning on the first computer device, making a request throughthe server (e.g., for a good and/or service), making a request and/oroffering a service via text, email, fax, and/or any other suitablemethod, and/or otherwise connecting to the server. Indeed, in someembodiments, the first computer device establishes a connection with theserver when a user opens an app on the first computer device and/ormakes a request or an offer through that device.

FIG. 5 shows that, in some embodiments, the method 500 continues at step504 as the user of the first device 365 makes a request and/or receivesa request through the first device. Where the user makes a request, theuser can make any suitable request (depending on the circumstances andthe functionality of the first device). By way of non-limiting example,the user may request and/or receive a request: for one or more rides(e.g., to get and/or give a ride via an UBER® vehicle, a LYFT® vehicle,a taxi, a bike taxi, and/or in any other suitable manner), meetings,visits, appointments, dates, bids, products (e.g., one or moreconcessions, groceries, items, tickets, and/or virtually any othergoods), services (e.g., one or more deliveries, repairs, massages,consultations, and/or virtually any other services); and/or othersuitable item or service; to be divided into groups; to be sent to alocation; to escort a minor; to enter a queue; and/or the user may askfor, offer, and/or otherwise make or receive any suitable request.

Continuing with FIG. 5, that figure shows that, in some embodiments, themethod 500 continues at step 506 as the first device (e.g., device 365)receives an identifier (e.g., an identifier that coordinates with anidentifier provided to one or more other computer devices (e.g., thesecond computer device) of users who have agreed to the request orotherwise been assigned to the transaction with the first device.

FIG. 5 shows that, in some embodiments, the method 500 further includesdetermining whether one or more additional optional steps (as discussedbelow) are to be performed before the transaction is complete. If thereare additional steps to be performed, the method continues to steps 510and 512. If there are no additional steps to be performed (and/or if theadditional steps are complete), the method continues to step 514, wherethe system (e.g., the first computer device 365, the second computerdevice 375, the server 385, and/or any other suitable portion of theoverall system) determines whether the transaction (and/or a portionthereof) is complete (e.g., whether the parties with coordinatingidentifiers on (or provided by) their various computer devices wereactually able to meet each other). If the transaction is not deemedcomplete, the method can continue in any suitable manner, including,without limitation, by returning to step 504 (and/or any other suitableportion of the method). That said, if the system determines that thetransaction is complete (e.g., the applicable parties have identifiedeach other), FIG. 5 shows the method 500 ends (e.g., as shown at step516), such that the method can be repeated and/or otherwise berestarted.

As mentioned, the described methods (e.g., methods 400 and 500, as wellas all other methods described herein) can be modified in any suitablemanner. In this regard, while FIGS. 4 and 5 show that, in someembodiments, the described systems and methods include providing one ormore additional steps before and/or after the parties in a transactionhave received coordinating identifiers, such additional steps can takeplace at absolutely any suitable time or times in the methods. Moreover,such additional steps can include any suitable step that allows thedescribed systems and methods to help parties identify each other(and/or a desired good, service, object, and/or location).

As an example of an optional step, some embodiments of the describedsystems and methods are configured to randomly pick the coordinatingidentifiers (e.g., to pick matching symbols with matching color schemes)that are provided to each of the computer devices in a transaction fromone or more databases. In some other embodiments, however, the describedsystems and methods are configured to select the coordinatingidentifiers based on one or more preferences, demographics, and/or otherinformation provided by and/or otherwise relating to one or more partiesto the transaction.

Indeed, in some embodiments, the described methods involve theadditional step of allowing one or more users to input preferencesand/or other information (e.g., demographic information and/or any othersuitable information) and/or of allowing the system to otherwise gaininformation about the user and/or the user's device. In this regard, theusers (or parties to one or more transactions) can input (and the systemcan otherwise obtain) any suitable preferences and/or information abouta particular user (and/or the user's device), including, withoutlimitation, the user's favorite colors; color schemes from a favoriteteam of the user; whether or not the user is color blind and shouldthereby be prevented from receiving identifiers with certaincolors/color schemes that would be difficult to see; whether the user isblind and should receive audio and/or haptic identifiers; the user'spreferred symbols; the user's desired identifier genres; the user'sdesired symbols; the users desired characters; the user's desired font;the location of the user's device; and/or any other suitable preferenceand/or other information. Additionally, in some embodiments, thedescribed systems and methods allow users to provide (and/or the systemto otherwise obtain) information about their age, gender, ethnicity,wage, Internet browsing history, and/or any other suitable informationthat may be useful in personalizing identifiers to such users and/or atransaction.

In some embodiments in which the described systems and methods allowusers to enter (and/or that otherwise allow the system to obtain)preferences and/or other information useful for identifier selection,the described systems and methods can select coordinating identifiersfor all parties to an interaction based on the preferences and/orinformation obtained from any number of parties to the transaction. Insome embodiments, however, the described systems provide identifiers toall parties to a transaction based on the preferences of one party tothe transaction (e.g., a patron, the purchase, the passenger, and/or anyother suitable party).

In some embodiments, the described systems and methods include, as partof the process for selecting identifiers, an additional step of checkingconditions (e.g., light, weather, time of day, and/or any othercondition) associated with one or more computer devices in a transaction(e.g., computer devices 365 and 375), and then selecting and/ormodifying the coordinating identifiers based on such conditions. By wayof non-limiting example, where any portion of the described systemsdetermines that a computer device is in a place with snow, the systemcan determine to use a dark identifier, as opposed to a whiteidentifier. In another example, if the system determines that a computerdevice participating in a transaction is in a place with a lot of light,the system will automatically modify/change the coordinating identifiersto help them be readily visible.

Where the described systems and methods are configured check one or moreconditions associated with one or more computer devices (e.g., the first365 and/or second 375 devices) in a transaction in order to selectand/or modify an identifier, the system may check such conditions in anysuitable manner, including, without limitation, by checking the time ofday as recorded by the computer system (e.g., server 385), anyapplicable computer devices (e.g., the first 365 and/or second 375devices), and/or any other suitable source; by checking weather, and/orlight locations (e.g., via one or more weather apps, websites, RSSfeeds, news websites, and/or other suitable sources) based upon alocation of one or more computer devices associated with a transaction;and/or in any other suitable manner.

In another example of a method used to select identifiers for atransaction, some embodiments of the described systems and methods areconfigured to check a location (e.g., via GPS coordinates,multilateration, localization, information provided by a user, and/orany other suitable method) of one or more computer devices (e.g., thefirst 365 and/or second 375 devices) in a transaction and to providecorresponding identifiers that relate to a location, an intendedlocation, an event (e.g., a sporting event, a play, a parade, a concert,a venue, and/or any other suitable event), a landmark, a touristattraction, a school, a school mascot, a flag, a business, and/or anyother suitable place and/or event that is en route, at a beginninglocation of, at a final location, and/or that otherwise associated witha party to a transaction. For instance, if some embodiments of thesystem determine that a potential passenger is just exiting (or evennear) an event (e.g., a football game), the system provides thatpassenger and any other party to the transaction (e.g., the driver) withan identifier relating to that event (e.g., a symbol of a footballhelmet, a football, a goal post, a player number, a jersey, a teamcolor, a team mascot, and/or any other suitable identifier relating tothe event). In another example, as the described systems and methods areused to determine that a party to a transaction is visiting anestablishment (e.g., Starbucks and/or any other establishment), thedescribed systems and methods may provide one or more parties to thetransaction with an identifier comprising a logo, trademark, servicemark, color scheme, and/or other identifier of that establishment.

In another example of a suitable optional step, in some embodiments, thedescribed systems and methods are configured to automatically modify(e.g., change; flash; blink; beep; make a sound; play music; display amessage (e.g., “Your car has arrived”, “Your table is ready”, etc.);combine identifiers (e.g. by placing matching portions of an imagetogether, by associating complementary identifiers with each other(e.g., by showing a first identifier comprising a basketball go througha second, hoop-shaped identifier or otherwise), and/or to otherwisecombine identifiers); alternate with other identifiers, and/or tootherwise modify the coordinating identifier provided to one or more ofthe computer devices (e.g., the first 365, second 375, and/or all otherdevices) involved in a transaction. In this regard, identifiers can becaused to be modified at any suitable time, including, withoutlimitation, as one or more of the computer devices (e.g., wirelessdevices or otherwise) in a transaction come into proximity with eachother, a turn in a queue of a party to the transaction approaches and/orarrives, after two or more computer devices participating in the sametransaction have been in proximity to each other for a set period oftime, and/or at any other suitable time.

Although in some embodiments, the described systems may only cause thecoordinating identifiers to be modified once the applicable computerdevices (e.g., a first and a second smart phone) are within a setdistance from each other, in some other embodiments, the coordinatingidentifiers are configured to be modified multiple times as two or morecomputer devices of a transaction come closer together. By way ofnon-limiting example, in some embodiments in which a first device 365 ina transaction is held by a car driver and a second device 375 is held bya potential passenger, the passenger's and/or the driver's device maybegin to flash their coordinating visual identifiers; brighten, focus,and/or otherwise change the appearance of the identifiers; alternate theidentifiers with one or more other identifiers; display a message withthe identifier, between identifiers, and/or at any other suitable time;beep; vibrate; and/or to otherwise modify such identifiers more and more(e.g., more and more quickly, brightly, louder, and/or in any othersuitable manner).

Moreover, in some embodiments, once two or more computer devices (e.g.,computer devices 365, 375, and/or any other suitable computer devices)in a transaction come within a set distance from each other and/oranother trigger has been met (e.g., a specific position in a queue hasbeen achieved, a set time in proximity to another party of a transactionhas occurred, and/or any other suitable modification factor has beenmet), one or more of the coordinating identifiers (e.g., allidentifiers) in the transaction are modified (e.g., flash at asignificantly faster rater, include one or more vibrations, include oneor more sounds, include one or more messages, etc.) to indicate that twoor more parties to the transaction have met, arrived at a location, arein proximity, are next in a queue, are advancing in a queue, and/or thatany other applicable modification event has or will occur.

In one example, as a car carrying the first device (e.g., computerdevice 365) approaches a passenger having the second device (e.g.,device 375), the first and second devices begin to flash (and/orotherwise modify) the coordinating identifiers (e.g., images, coloredscreens, etc.) of one or both devices more and more rapidly until thetwo parties are within a set distance from each other—at which time, thecoordinating identifiers of one or both parties begin to flash (and/orotherwise be modified) at a maximum rate. Thus, in some suchembodiments, as the parties look at each other's identifiers, theparties are readily able to recognize the corresponding identifier oridentifiers of other parties in the same transaction (even if otherparties participating in other transactions are nearby and displayingtheir assigned identifiers).

Where the described systems and methods automatically modifycoordinating identifiers in one or more transactions based on aproximity between two or more computer devices (e.g., the first, second,and/or other devices) in a transaction (and/or based on an estimatedtime to meeting, a placement in a queue, and/or any other suitablefactor directing identifier modification), the systems and methods canmodify all of the identifiers of the transaction in the same (orsimilar) manner; can modify all of the identifiers, though notnecessarily in the same manner; and/or can modify (in the same ordifferent manners) the identifiers presented by or less than all of thedevices in the transaction. That said, in some embodiments, when theidentifier provided by one of the devices in the transaction ismodified, all of the other identifiers provided by the other devices inthe transaction are also modified in the same (or a very similar)manner—thus, making it easy for parties to readily recognize theidentifiers of the other party or parties to their transaction.

While the described systems and methods can function in any suitablemanner to modify the coordinating identifiers in a transaction based onthe proximity of two or more parties to the transaction (and/or anyother set modification factor), FIG. 6 shows (at step 602) that, in someembodiments, the method 600 comprises setting one or more set distances(and/or other modification factors (e.g., estimated times until ameeting, specific placements in a queue, and/or any other suitablefactor)) that determine when (and how) the coordinating identifiers in atransaction will be modified. In this regard, the distances (and/orother modification factors) can be set any suitable threshold (e.g., atany suitable distances, times, queue positions, etc.) and can be set inany suitable manner, including, without limitation, by being preset,being set at the computer system (e.g., server 385), being set at thecomputer device of one or more parties to the transaction, and/or in anyother suitable manner.

At step 604, FIG. 6 shows that, in some embodiments, the method 600continues as a distance (and/or measurable characteristic relating to amodification factor) is tracked (e.g., via GPS coordinates,multilateration, localization, GOOGLE® maps, APPLE® maps, and/or anyother suitable method), and the system (at step 606) determines whetheror not at least two devices in a transaction have come to one of the setdistances (and/or another modification factor has been met).

If the system determines at step 606 that the devices are not within aset distance (and/or that another modification factor has not been met),FIG. 6 shows the method 600 returns to step 604. In contrast, and inaccordance with some embodiments, if the system determines that at leasttwo devices in a transaction are within a set distance (or that one ormore other modification factors have been met), the system determines(at step 608) whether such set distance (or other factor) is the triggerfor the final identifier modification.

If, at step 608, the system determines that space between the devices inthe transaction (and/or another modification factor) is not the triggerfor the final identifier modification, the method 600 continues to step610, and the identifiers in the transaction are modified, even if onlystepwise (e.g., such that the identifiers flash a little more quickly,an estimated time to meeting is updated, a sound volume of an audibleaspect of the identifier increases, and/or any other suitablemodification occurs).

If, however, the system determines that the distance between two or moreparties in the transaction is close enough (and/or that anothermodification factor has been met) to trigger the final modification,then (as shown at step 612), the method 600 continues as the finalidentifier modification is provided to the devices in the method (e.g.,a notification is presented, the coordinating identifiers on all devicesflash (in unison or otherwise) at a rapid pace, a video clip oranimation is shown, and/or any other suitable modification is providedto show that two or more computer devices (e.g., phones, tablets, etc.)in the transaction are in close proximity to each other (and/or thatanother modification factor has been met).

As another example of a suitable optional step that can be included inthe described systems and methods, in some embodiments, the describedsystems allow users of one or more computer devices (e.g., devices 365,375, and/or any other suitable device) in a transaction to request thatthe coordinating identifiers associated with a transaction bedynamically changed, replaced, updated, and/or otherwise modified, atany suitable time and in any suitable manner. By so doing, one or moreparties to a transaction can request an identifier modification, seethat his or her identifier and the identifiers of one or more otherpurported parties to the transaction have changed in the same manner,and thereby confirm (e.g., as an additional layer of security) that theother party or parties having the newly modified and matchingcoordinating identifier are all part of the same transaction.Accordingly, if any party to a transaction has any doubts that someoneelse with a matching coordinating identifier is truly a party to thesame transaction as the party in doubt, the party in doubt can easilyremove his or her doubts by requesting for an identifier modification(e.g., via the computer device of the party in doubt and/or any otherpurported party to the transaction) and then checking to see that theupdated identifiers still coordinate (or match).

In another example of a suitable optional step, some embodiments of thedescribed systems and methods are configured to check and ensure that,unless such computer devices are part of a specific transaction, one ormore computer devices in proximity to one or more other computer devices(e.g., the first 365 and/or second 375 devices) participating in thespecific transaction do not have an identifier that coordinates with thecoordinating identifiers assigned to that specific transaction. In thismanner, the described systems and methods can prevent parties that arein the same general vicinity and that coincidentally have thecoordinating identifiers from inadvertently believing that parties areactually part of the same transaction.

While the described systems and methods can ensure that the coordinatingidentifiers of one transaction do not coordinate (or match) with anidentifier of another transaction when one or more devices from theseparate transactions are in close proximity to each other, FIG. 7 showsa representative embodiment of a method 700 that involves (as shown atstep 702) determining the location of the parties to a transaction. Inthis regard, the system can determine the location of the computerdevices pertaining to the parties in a first transaction in any suitablemanner, including, without limitation, by: checking GPS coordinates ofthe devices in the transaction(s), checking IP addresses of suchdevices, multilateration techniques, localization techniques, usinginformation provided by one or more users in the first transaction(e.g., addresses, current location, desired location, etc.), checkingproposed travel routes of the devices (e.g., via GOOGLE® maps, APPLE®maps, electronic maps, electronic schematics, electronic plans, etc.)and/or by any other suitable method.

Step 704 shows that, in some embodiments, the method 700 continues asthe system (e.g., the computer system or server 385 and/or one or morecomputer devices) determines whether or not any third party devicepertaining to another transaction (e.g., a second and/or any othertransaction) is (or may move to be) in proximity to a device pertainingto the first transaction. If the system determines that a third-partydevice is in proximity (or that may likely come into proximity) with adevice of the first transaction, step 706 shows the method 700 includeschecking the identifier of the third-party device, and step 708 showsthat the method 700 then includes ensuring that the identifiers of thefirst transaction do not match with the third-party identifier. Whilethis can be accomplished in any suitable manner that allows the varioustransactions in proximity to each other to each have distinctidentifiers, in some embodiments, the system simply selects anidentifier for the first transaction that does not match the thirdparty's identifier. In some embodiments, the system changes theidentifier of the third party, along with the coordinating identifiersof any other parties to the third-party transaction. In still otherembodiments, the system changes the identifiers of the third-partytransaction and further provides the first transaction with anidentifier that does not match the identifiers that are newly assignedto the third-party transaction.

Whether or not the system determines at step 704 that there is a thirdparty in a separate transaction and who is in proximity (or who maylikely or even possibly come into proximity) with one or more parties tothe first transaction, FIG. 7 shows that, in some embodiments, themethod 700 continues as the system assigns an identifier to the currenttransaction (e.g., the first transaction). As discussed above, as thesystem assigns an identifier to the first transaction, the systemensures that the identifier of the first transaction does not coordinatewith an identifier of the third-party transaction (which has one or moreparties who are within a set area with a party of the first transactionand/or who may likely cross paths or come into proximity with a party ofthe first transaction (e.g., as determined based on planned partyroutes, on set territories, and/or otherwise)). Once such an identifieris assigned to the first transaction, FIG. 7 at step 712 shows that someembodiments of the method 700 end or continue on (as applicable) inmethods 400 and/or 500.

Returning to the non-limiting description of optional steps that can beincluded in the described methods, in some embodiments, the describedsystems and methods are configured to allow the remote computer system(e.g., the computer system or server 385) and/or one or more computerdevices (e.g., the first 365 and/or second 375 computer devices) to passan assigned identifier to one or more other devices. Although in someembodiments, the system is configured to pass the identifier from afirst device to one or more other devices without leaving the identifieron the first device (e.g., such that the first device is no longer aparty to the transaction), in some other embodiments, a user of thefirst computer device is able to pass or otherwise send an identifierreceived from the remote computer system to one or more other computerdevices, while still maintaining the identifier on the first device(e.g., such that the first device and the newly invited device ordevices are all parties to the same transaction). In some otherembodiments, however, the remote computer system and/or one or moreother devices pertaining to a transaction are able indicate that one ormore parties in the transaction cannot pass their identifier on toanother.

A feature that allows the computer system (e.g., server 385) and/or oneor more parties to a transaction to pass an identifier of thetransaction to one or more other parties (e.g., to one or more devicesthat were not originally part of the transaction) can be useful in awide variety of circumstances. In one example, if a potential riderdesires to share a car ride with another, the potential rider may inviteanother person to the transaction by sending a copy of the identifier tothe other person's computer device (e.g., via near field communication,BLUETOOTH® communication, a text, an email, an RF communication, and/orin any other suitable manner). In another example, where a potentialrider desires to allow some else to get a ride first, the potentialrider can pass his or her identifier to another person's device and thenenter into another transaction to get a ride, In still another example,where a transaction is set up to orchestrate the delivery of a packagefrom a first party to a second party via a third party (e.g., acourier), and the third party is only able to carry the package on aportion (or leg) of the trip, the third party can (in some embodiments)pass the package and the identifier pertaining to the transaction to afourth party (e.g., one or more other approved couriers), such that whenthe fourth party delivers the package to the second party, the secondand fourth parties can compare identifiers and ensure they are meetingthe right people and that the package is being delivered to the properperson.

Where the remote computer system (e.g., the server 385) and/or one ormore parties to a transaction are able (e.g., via their computer devices365, 375, etc.) to pass an identifier of the transaction to one or moreother parties, the described systems and methods can treat the partiesthat have newly entered into the transaction in any suitable manner.Indeed, in some embodiments in which the described systems and methodsare tracking a location of, billing, sending information to, receivinginformation from, preventing undesirable identifier matching with,and/or otherwise interacting with one or more parties (and/or computerdevices) who originally belonged to a transaction, the described systemsoptionally begin to interact in one or more of the same ways with thedevice of the party who has newly entered the transaction. By way ofnon-limiting example, where one party riding in a car (e.g., via anUBER® ride or otherwise) invites another party to join in the car rideafter the first rider has already ridden for a period of time, thesystem can begin to track the new rider so as to just bill the new riderfor the distance he or she actually travels in the car.

As another example of a suitable optional step, some embodiments of thedescribed systems and methods allow one computer device (e.g., the firstcomputer device 365) to be part of multiple transactions and to displayand/or otherwise provide an identifier that coordinates with theidentifiers of each of the multiple transactions. Such feature may beuseful in a variety of circumstances and for a variety of purposes. Byway of non-limiting illustration, when multiple people in an event(e.g., a stadium, concert hall, or other location) each use thedescribed systems and methods to set up an individual transaction (e.g.,to purchase a concession item or otherwise), and one server becomes aparty to each such transaction, the described systems and methods canhelp ensure that the server is able to find and identify each party andvice versa.

Where one device (e.g., a first device 365 and/or any other suitabledevice or devices) is able to participate in multiple transactions, thedescribed device can display and/or otherwise provide the identifiersfor the various transactions in any suitable order and/or at anysuitable time. By way of non-limiting example, a first device candisplay and/or otherwise provide the identifiers of one of thetransactions to which the first device is a party based upon: aproximity of the first device to another device that is in a transactionwith the first device (e.g., showing the identifier assigned to theclosest device to the first device), the queue placement of anotherparty who is in a transaction with the first device (e.g., showing theidentifier of the party or transaction that is next in the queue), arandom determination of which identifier to show, and/or any othersuitable criterial and/or determination.

In some embodiments in which the described systems and methods allow thefirst computer device 365 (and/or any other computer device) to be partof, and have coordinating identifiers for, multiple transactions, thedescribed systems and methods optionally allow and/or ensure that thefirst computer device displays and/or otherwise provides the identifiercoordinating to the transaction of the closest device that is part ofone of the multiple transactions to which the first device is a party.By way of non-limiting example, where a server (or other party) who isparticipating in ten transactions (e.g., is assigned to deliver goods toten parties) approaches a party to a first of the ten transactions, theserver's computer device (e.g., phone, tablet, and/or other computerdevice) will display the identifier corresponding to that firstparty—thus the server and the first party will be able to readilycompare identifiers and recognize each other. In this example, once theserver has provided the first party with the purchased goods orservices, the server's device can then display or otherwise provide theidentifier for (and/or map with a route to) the next closet applicableparty (e.g., device) to the server.

Where the described systems and methods allow a single device (e.g., thefirst 365 or second 375 device) to participate in multiple transactionsand to display and/or otherwise provide the identifier to closestapplicable party, the systems and methods can be performed in anysuitable manner. In this regard, FIG. 8 shows a representativeembodiment of one such method 800. In particular, FIG. 8 shows that, insome embodiments, the method of this optional step begins at step 802 asa first device enters into multiple transactions, and continues at step804 as the first device receives identifiers for the multipletransactions.

At step 806, FIG. 8 shows that, in some embodiments, the method 800continues as the system tracks the locations of (and/or the queueplacement, status of an applicable order, and/or any other suitableinformation pertaining to) each of the parties in the multipletransactions to which the first device is a party. As described above,this tracking can be accomplished in any suitable manner, including,without limitation, by: checking GPS coordinates of the devices in thetransaction, checking IP addresses of such devices, multilaterationtechniques, localization techniques, using information provided by oneor more users in the transaction (e.g., addresses, current location,desired location, etc.), receiving information from the applicabledevices, receiving information from the server 385, and/or any othersuitable method.

At step 808, FIG. 8 shows that, in some embodiments, the method 800continues as the system determines whether one device of the multipleparties to which the first device is party is closer to the first device(and/or whether one party is closer in a queue to that parties turn thananother, whether the status of one order has progressed further thananother, and/or whether there is any factor that indicates that onetransactions identifier should be displayed and/or otherwise providedbefore the identifier of another transaction). If there is not, then thefirst device can display or otherwise provide any material, including,without limitation, maps to one or more parties in applicabletransactions, estimated times until an order is ready, identifiers formultiple parties (e.g., providing multiple identifiers at once, forinstance on a split screen; alternating through the identifiers beingprovided; displaying any of the applicable identifiers (e.g., as shownat step 810); and/or in any other suitable manner); and/or any othersuitable material. In some embodiments, if the system determines that noparty from the multiple transactions to which the first device is aparty is closer than another (or should otherwise have its identifierdisplayed before another identifier), the method continues as the systemcontinues to check the locations of (and/or other suitable informationrelating to) the multiple parties, with respect to the first device orotherwise.

Once the system (e.g., the server 385 and/or any other suitable portionof the overall system) determines that the device (e.g., the seconddevice 275) of one of the multiple transactions to which the firstdevice 365 is a party is closest to the first device (and/or thatanother factor relating to the second device otherwise meets a setcriterion indicating that the identifier of the second device should beshown before that of another transaction), step 812 of FIG. 8 showsthat, in some embodiments, the method 800 continues as the first deviceprovides the identifier of the closest party (and/or of the transactionthat is next in a queue and/or that otherwise meets a set criterionindicating that the identifier of a certain transaction is to bedisplayed next).

Next, at step 814, after the first party with the first device hascompleted a transaction (or at least a portion of such transaction) withone party, FIG. 8 shows that, in some embodiments, the described systemsand methods include determining whether any other transactions to whichthe first device (and first party) are a party are still open. If thereare, FIG. 8 shows that some embodiments of the method return to step806. Once, however, all of the transactions to which the first party isa party are complete, FIG. 8 (at step 816) shows that, in accordancewith some embodiments, the method 800 ends and/or returns to method 400and/or 500.

As another example of a suitable optional step that can be included inthe described systems and methods, some embodiments of the describedsystems and methods are configured to track and record (e.g., in memory220 of the server 385, in memory of one or more computer devices in atransaction, and/or elsewhere) at least one of the times, paths,distances, frequencies, and/or other recordable characteristics of whentwo or more computer devices in a transaction (e.g., devices comprisingcoordinating identifiers) are in a desired proximity to (and/or out of adesired proximity with) each other. Such a feature can be useful for avariety of purposes, including, without limitation, determining that atransaction has been completed, tracking and otherwise helping protectthe safety of parties involved in one or more transactions, ensuringthat bills are accurate, and/or for any other purpose. In this regard,the described systems can track and record information relating tomeetings between (and/or separation from) parties to a transaction inany suitable manner, including, without limitation, by recording GPScoordinates of the devices in the transaction, recording IP addresses ofsuch devices, multilateration techniques, localization techniques,recording information provided by one or more users in the transaction(e.g., addresses, current location, desired location, confirmation ofreceipt, etc.), and/or any other suitable method.

In another example of a suitable optional step, some embodiments of thedescribed systems and methods allow at least one of the remote computersystem (e.g., the server 385), a first device 365, a second device 375,and/or any other computer device in the system to provide one or moreidentifiers (e.g., visual, audio, touch, and/or other identifiers)through one or more objects (e.g., vehicles, speaker systems, watches,ear pieces, headsets, display screens, pagers, projectors, and/or otherdevices) that are in signal communication with at least a portion of thedescribed system (e.g., at least one of the remote computer system, thefirst computer device, and the second computer device).

In one non-limiting example illustrating how the described systems andmethods can provide a coordinating identifier through an object that isin signal communication with a portion of the system, in someembodiments, the remote computer system (e.g., the server 385), thefirst computer device 365, and/or the second computer device 375 areconfigured to control a car's lights, horn, speakers, PA system, and/orother visual and/or audio outputs to help provide a coordinatingidentifier (and/or to otherwise alert a potential party to the car'spresence). For instance, in some embodiments, as such a car comes intoproximity with the computer device of another party that is part of atransaction with the computer device (or driver) being carried by suchcar, the car can be used to: flash its headlights (e.g., at the sametime the identifier on the intended passenger's phone or other deviceflashes, and/or in any other suitable manner); make a sound (e.g., playmusic that corresponds to music being played by the potentialpassenger's phone, and/or make any other suitable sound); and/orotherwise provide a coordinated identifier and/or notify the intendedpassenger of the car's presence.

In another non-limiting example illustrating how the described systemsand methods can provide an identifier through an object that is insignal communication with a portion of the system, in some embodiments,the system is configured to provide one or more coordinating identifiersthrough one or more displays. For instance, in some embodiments, a cardriver who is part of a transaction may receive a coordinatingidentifier on a first computer device 365 (e.g., the driver's phone),which, in turn, provides the same coordinating identifier to a displaythat is visible from outside the car (e.g., a display that is: placedfacing out from a window of the car, such as the windshield, passengerside window, etc.; a heads-up display shown on a car window; and/or inanother manner that is otherwise visible to potential passengers). Insome other embodiments, the coordinating identifier may be provideddirectly to such a display (e.g., without being provided to a separatecomputer device). In both such embodiments, the driver can provide thecoordinating identifier, without being unduly distracted (e.g., tryingto find his or her phone and to lift it up so that intended passengerscan see it).

In yet another non-limiting example illustrating how the describedsystems and methods can provide an identifier through an object that isin signal communication with a portion of the system, in someembodiments, a portion of the system is configured to communicate withan output that is capable of providing a coordinating identifier (e.g.,one or more displays, speakers, lights, and/or other suitable outputs).By way of example, in some embodiments in which a group of people arebeing sent to various locations and/or are otherwise being divided intosmaller groups (e.g., to break up groups in a class, conference, and/orfor any other suitable purpose), a portion of the system (e.g., theserver 385, the first computer device 365, etc.) can send variousidentifiers to one or more identifier outputs (e.g., displays) and cansend coordinating identifiers to the various computer devices (e.g.,phones) of such people—thus directing the various people to theircoordinating identifier and/or the output providing such identifier.

Returning again to the non-limiting description of the optional stepsthat can be included in the described methods, in some embodiments, thedescribed systems and methods are configured to use of facial, optical,Wi-Fi, BLUETOOTH®, and/or visual recognition technology to identify oneor more parties to a transaction, to cause the coordinating identifierto be provided, to trigger a modification of the coordinating identifieror identifiers in a transaction, and/or for any other suitable purpose.While this can be accomplished in any suitable manner, in someembodiments, the described systems and methods include obtaining andanalyzing (e.g., via software accessed through any suitable portion ofthe described system) an image of a desired object (e.g., a picture of aparty to a transaction, such as a driver, a passenger, and/or any othersuitable party; a car associated with a party to the transaction; alandmark associated with the transaction; and/or any other suitableobject or objects).

Once an image of the desired object has been obtained and analyzed, someembodiments of the described system are configured to capture images(e.g., via a camera and/or sensor in signal communication with thesystem, for instance through a computer device of a party to thetransaction) and to notify one or more parties to a transaction oncethat object has been detected. In one example, as an intended passengerholds up his or her phone (e.g., displaying an identifier or otherwise)and a camera and/or other sensor on that phone captures an image of theintended car and/or driver, the described systems and methods can alertthe intended passenger that his or her car has arrived (e.g., byflashing and/or otherwise modifying the identifier, posting a message,and/or in any other suitable manner).

In still another example of a suitable optional step, some embodimentsof the described systems and methods are configured to provide one ormore computer devices in the described system with promotionalmaterials, advertisements, pop-up ads, coupons, information, readingmaterial, and/or any other suitable material in connection with anidentifier and/or in any other suitable manner. The content, timing, andother factors relating to the provision of such material can bedetermined in any suitable manner, including, without limitation, bybeing randomly selected; being selected based on one or more locations,desired locations of, events in proximity to, retailers and/or serviceproviders in proximity to, preferences, and/or any other factorsrelating to one or more parties of a relevant transaction; and/or in anyother suitable manner. Indeed, in some embodiments, the provision ofsuch material is personalized for the individual receiving it (e.g., bybeing based on a user's browsing history, a user's preferences, a user'slocation, and/or in any other suitable manner).

In yet another example of a suitable optional step, some embodiments ofthe described systems and methods are configured to encrypt (e.g., viasymmetric key, encryption, public key encryption, and/or otherwise)and/or to otherwise encode information being relayed about one or moreparties and/or coordinating identifiers. In this manner, the describedsystems and methods can help prevent others from hacking into the systemto thereby create fake identifiers. Thus, some such embodiments providean additional layer of safety and confidence for parties totransactions.

In still another example of a suitable optional step, some embodimentsof the described systems and methods are configured to ensure that oneor more identifiers are only provided within a certain location and notoutside that location. By way of non-limiting illustration, FIG. 9 showsthat, in accordance with some embodiments, some identifiers are onlyprovided within one or more certain geographic locations 90 (which mayinclude, but is not limited to, one or more rooms, buildings, radii, setpieces of land, set neighborhoods, specific cities, portions of a venue,specific states, specific countries, and/or any other suitablelocations). In some embodiments, however, as shown in FIG. 9, while oneor more identifiers are provided within a specified geographic area 90,and while such identifiers are not available in a zone 92 that isoutside, surrounds, flanks, is adjacent to, and/or that is otherwisenear the specified geographic area, such identifiers can (in someembodiments) be available in one or more locations 94 that are outsideof such a zone 92. Accordingly, in some such embodiments, the describedsystems and methods can further prevent parties from improperlyreceiving coordinating identifiers with one or more other parties whoare not all participating in the same transaction.

In another example of a suitable optional step, some embodiments of thedescribed systems and methods allow one or more parties within atransaction to text, instant message, e-mail, call, send audio to, sendimages to, video chat with, send updates to, provided new locationinformation, provide new offer information to, provide new requestinformation to, and/or to otherwise communicate with each other.

In even another example of a suitable optional step, the describedsystems and methods can dispose of identifiers in any suitable manner(e.g., when the identifiers are modified, when a transaction iscomplete, and/or at any other suitable time). Indeed, in someembodiments, once an identifier is no longer needed in a particulartransaction (and/or portion of a transaction), the identifier can: bereused (e.g., by the same party and/or different party), dissolve,self-destruct, be saved in a collection of identifiers received by eachindividual party, and/or otherwise handled in any suitable manner.Indeed, in some embodiments, the identifiers provided to each party aresaved in an account, on that party's device, and/or otherwise (e.g.,like stamps in a passport).

In another example of a suitable optional step, some embodiments of thedescribed systems and methods are configured to learn from priortransactions and to update estimates, determine parties in atransaction, predict actions of parties in a transaction, and/or tootherwise modify the transaction (e.g., to change when coordinatingidentifiers are given to the parties, to change estimated times ofarrival, to change the timing in which notices are given to one or moreparties, to modify proposed routes one or more parties can take to meetanother party in a transaction, and/or to otherwise modify and/oroptimize the transaction in any suitable manner).

In yet another example of a suitable optional step, some embodiments ofthe described systems and methods are configured to track two or morecomputer devices (e.g., 365, 375, etc.) in one or more transactions andto determine the fastest and/or any other preferred route between theparties (and/or one or more desired locations). In such embodiments, thesystem may determine such a route in any suitable manner, including,without limitation, by tracking the parties' computer devices (e.g., viaGPS, multilateration, etc.); via mapping software (e.g., GOOGLE® maps;APPLE® maps; software utilizing venue maps, building maps, schematics,and/or any other suitable information; and/or any other suitable mappingsoftware).

The described systems and methods can be useful in virtually anysuitable circumstances in which two or more parties want to identifyeach other (and/or one or more corresponding computer devices) withconfidence. Some non-limiting examples of situations in which thedescribed systems and methods may be used, include in the areas oftransportation (e.g., allowing one or more drivers and one or moreintended passengers to readily identify each other), courier services(e.g., allowing one or more senders and/or recipients to rapidly andconfidently identify one or more couriers and vice versa), eventticketing (e.g., where an identifier functions as one or more tickets),concessions (e.g., allowing one or more concession workers to identifyone or more patrons), and queue management (e.g., alerting parties whentheir turn in a queue has arrived and providing such parties with acoordinating identifier to identify them and/or their place in thequeue).

Indeed, in some embodiments, the described systems and methods are usedto help two or more parties identify each other for transportationservices (including, without limitation, via one or more UBER® rides,LYFT® rides, taxi rides, bus rides, airplane rides, ferry rides, biketaxi rides, rickshaw rides, horse and carriage rides, limo rides, hitchhiking, etc.). While the described systems and methods can be used withtransportation services in any suitable manner, FIG. 10 shows onenon-limiting example of a suitable method 1000 (e.g., as depicted from acomputer device of a potential passenger).

In particular, FIG. 10 shows that, in some embodiments, the methodbegins (at step 1002) as a potential passenger uses a first computerdevice 365 (e.g., a smart phone, tablet, and/or any other suitablecomputer device) to request a ride (e.g., by entering a desired pickuplocation, drop-off location, pick-up time, vehicle type, fare rate,whether or not the passenger desires to ride alone and/to split fairwith another passenger, and/or any other suitable information). Whilenot shown, a potential driver may also provide the described system withany suitable information (e.g., that the driver is willing to driveothers, the driver's location, the type of vehicle the driver isdriving, the number of seats in the vehicle, how far the driver iswilling to drive, how long the driver is willing to drive, and/or anyother suitable location).

At step 1004, FIG. 10 shows that some embodiments of the method 1000continue as the potential passenger and the selected driver enter into atransaction and the system provides the passenger and/or the driver withan estimated cost of the ride and an estimated pickup time.

Step 1006 shows, that in some embodiments, the described method 1000provides the parties to the transaction (e.g., the passenger and/ordriver) with estimated times (continuously or otherwise) until thepickup (e.g., in seconds, minutes, hours, and/or otherwise).Additionally, in some embodiments, the described systems and methods areconfigured to show one or more parties to the transaction (e.g., via thefirst device 365 and/or the second device 375) one or more maps,indicating the current locations of one or more parties to thetransaction, proposed travel routes, traffic delays, and/or any othersuitable information.

Although the described systems and methods can provide the variousparties to a transaction (e.g., via the first computer device 365, thesecond computer device 375, and/or any other computer device) withcoordinating identifiers at any suitable point before, during, and/orafter a transaction, step 1008 shows that, in some embodiments, thedescribed systems and methods provide the parties to the transactionwith (and/or modify the) coordinating identifiers when the distanceand/or estimated time between the various parties meets a specifiedtrigger point. Thus, step 1010 shows that, in some embodiments, theparties to the transaction (e.g., the driver and passenger) can readilyidentify each other (e.g., by holding up phones, displays, and/or othercomputer devices displaying and/or otherwise providing the coordinatingidentifiers, such that each party is able to readily see (and/orotherwise perceive) and match the identifier of the other party. At step1012, FIG. 10 shows the method 1000 can proceed in any suitable manner,including, without limitation, by recycling the identifiers, storing theidentifiers in accounts for one or more parties, requiring one or moreparties to pay a bill, and/or in any other suitable manner.

Although the method 1000 described in FIG. 10 describes a transactioncomprising two parties (e.g., a driver and a passenger), the describedsystems and methods can be modified to include any suitable number ofparties (e.g., any suitable number of drivers (e.g., for various legs oftrip and/or for any other suitable purpose) and/or any suitable numberof passengers (e.g., in the same or different transactions and with thesame and/or different coordinating identifiers)). Indeed, in someembodiments, one transaction comprises multiple parties (e.g., driversand/or multiple passengers) that all have the same coordinatingidentifiers. In other embodiments, however, a one party (e.g., thedriver) driver may be party to multiple transactions, which each have adifferent identifier (e.g., as described above with respect to themethod 800 in FIG. 8).

While the described systems and methods can be useful for severalreasons when used to identify parties in transactions relating totransportation, some embodiments provide several beneficialcharacteristics over some conventional methods for identifying one ormore potential drivers and passengers. Indeed, some conventional methodsfor identifying parties in a transportation transaction provide a driverwith a location of the passenger, and provide the passenger(s) with apicture of the driver's car and/or the driver, as well as with thedriver's license plate number. In some cases, however, such conventionalmethods have shortcomings. For instance, when using some suchconventional methods, a driver who pulls up to a large group of peoplewho are waiting for various drivers (e.g., a group of people who havejust left a large event), the driver may have to call out the name ofhis or her intended passenger to actually find the right passenger.

Additionally, under some conventional methods, where a large group ofpeople are waiting in the dark for their respective drivers, thepotential passengers may have a hard time identifying their driver. Forinstance, where multiple drivers have similar cars (e.g., TOYOTA®Priuses), it may be hard for passengers to readily identify theirride—especially in the dark where it may be hard to distinguish cars bycolor, where cars' headlights make it hard for passengers to read frontfacing license plates, where cars are lacking a front facing licenseplate, and/or for any other reason.

In contrast with some such conventional methods, some embodiments of thedescribed systems and methods provide each party to a transaction withcoordinating identifiers (e.g., a visual symbol and/or color scheme)that can be seen and/or otherwise perceived relatively easily (as theparties display their identifiers), and that can be readilydistinguished from other identifiers of other transactions. Accordingly,in some embodiments, no matter how dark the night, no matter how similarthe cars may appear, no matter how similar the various drivers mayappear, and no matter how many people are waiting for a ride, theparties to a transaction can readily and confidently identify and eachother.

Additionally, in some embodiments, even when users of devices (in anysuitable situation) cannot see and/or otherwise perceive the identifiersof other devices that are in proximity and/or potential proximity tosuch users (and/or such users' devices) and where such other devices arenot participating in the same transaction of such users, the describedsystems and methods are able to ensure that the identifiers of theseparate transactions do not coordinate with each other (e.g., byautomatically changing one transaction's identifiers, by preventingcertain identifiers from being used in another transaction, and/or inany other suitable manner). Accordingly, in some embodiments, thedescribed systems and methods are able, behind the scenes as it were, toprevent parties from improperly identifying and believing that one ormore parties belong to a certain transaction when they in fact do not.

With reference now to courier services, the described systems andmethods can be used to help parties trying to send, deliver, and/orreceive a package (and/or any other suitable goods and/or services) toreadily identify those who are part of an applicable transaction. Whilethe described systems and methods can be used in any suitable manner insuch circumstances, FIG. 11, shows that, in some embodiments, one suchmethod 1100 includes (as shown at step 1102) allowing one party torequest a pickup or drop off (e.g., of a package) and to indicate and/oragree to a time and place for the pickup/drop off, while another party(e.g., a courier) can communicate with the first party to agree toand/or to otherwise determine a pickup site and time.

Step 1104 shows that some embodiments of the described systems andmethods: track the locations of one or more parties to the transaction;create a dynamic history tracking movements and/or average times neededfor one or more parties to the transaction to travel certain places atcertain times; provide an estimated time to arrival; and/or otherwiseprovide information that facilitates the transaction. By way ofnon-limiting example, some embodiments of the described systems andmethods, indicate an estimated time until the courier will arrive at apickup spot and can even provide the person providing an item with anestimate of how long it will take that person to get to the pickup spot,indicating when such person should leave for the pickup spot.

Step 1106 shows that some embodiments of the method 1100 shown in FIG.11 include providing each party to the courier transaction (e.g., thecourier, the person providing a package or other item to the courier,and/or any other suitable party) with a coordinating identifier (e.g., avisible and/or other identifier that can be shown on a smart phone orother computer device), which can readily be identified by the variousparties of the transaction to ensure that the intended parties aremeeting (e.g., at the identified pickup spot).

As shown at step 1110, at any point in a transaction, one or moreparties to the transaction can pass a coordinating identifier to anotherparty (e.g., to another party's device). Accordingly, in someembodiments, multiple people may be involved in a transaction (e.g., tomake it more efficient, faster, more economical, more convenient, and/orto otherwise help complete the transaction). By way of non-limitingillustration, FIG. 12A shows that, in some embodiments, multiplecouriers (as illustrated by the circles at the left in column 1) use thesame and/or a different coordinating identifier (e.g., the variousletters in FIG. 12A showing an optional embodiment in which eachtransaction comprises a separate identifier) to pick up packages (e.g.,by matching identifiers with applicable parties). In some suchembodiments, the couriers then optionally pass the packages and thecorresponding coordinating identifiers onto one or more other couriers(e.g., couriers who have the same coordinating identifiers, as shown incolumn 2), who in turn, optionally provide the packages (and/or otheritems) to one or more other couriers who are passed or otherwise havematching identifiers (e.g., as shown in columns 3-9), until the finalcourier (e.g., shown in column 9) is able to provide the package (and/orother item) to its intended recipient (not shown) by having the finalcourier and the intended recipient match identifiers, as shown at step1114 in FIG. 11. Thus, although a single courier can use the describedsystems and methods to take an item from its sender to its recipient, insome other embodiments, the described systems and methods are configuredto allow multiple couriers to gather and deliver multiple packages in anefficient manner.

The method 1100 of FIG. 11 can be modified in any suitable manner. Inhis regard, step 1112 shows that, in accordance with some embodiments,the described systems and methods can provide estimated pickup times,arrival times, drop-off, optional parties (e.g., couriers, etc.) toinclude in the transaction, and/or any suitable information that may beapplicable to a transaction.

As another example of a suitable method for using the described systemsand methods in courier services, FIG. 12B illustrates a method 1200 thatincludes (as shown at step 1202) providing a party-identificationapplication (e.g., a website, a mobile app, an app, and/or othersoftware that performs at least some of the described systems andmethods) to any suitable number of devices. Indeed, in some embodiments,the described systems include making the party-identificationapplication available to a first device (e.g., a device of a partyintending to send goods and/or services (which may collectively andindividually be referred to herein as an item) to a third party), asecond device (e.g., a device of a deliverer who plans on taking theitem (at least partway) to the third party, and a third device (e.g., adevice of an intended recipient of the item).

At step 1204, FIG. 12B shows that some embodiments of the method 1200include linking and/or otherwise placing the first, second, and thirddevices into a transaction with each other. Additionally, at step 1206,FIG. 12B shows that some embodiments of the method 1200 includeproviding coordinating identifiers to the devices in the firsttransaction. In this regard, the coordinating identifiers can beprovided to the devices in any suitable manner (e.g., via a processor ofthe computer system 385, via a processor or one or more of the devices,and/or in any other suitable manner). In this regard, when thisdescription refers to a function being performed by a processor of thecomputer system and/or a server, it should be noted that were possiblesuch a function may be performed by one or more processors of a computerdevice (e.g., 365, 375, etc.). In some embodiments, a first set ofcoordinating identifiers is provided to the first and second devices inthe first transaction (e.g., to the devices of a sender and deliverer ofan item) and a second set of coordinating identifiers is provided to thesecond and third devices (e.g., the devices of the deliverer and theintended recipient of the item). Although in some embodiments, the firstand second sets of identifiers comprise different identifiers that arereadily distinguishable from each other, in some other embodiments, thefirst and second sets of identifiers coordinate with each other.

In some embodiments, not shown in FIG. 12B, one or more parties to thefirst transaction are able to optionally pass an identifier from theirdevice to another device such that the other device becomes part of thetransaction (see e.g., FIGS. 11 and 12A). For instance, in someembodiments, the second device (e.g., the device of the deliverer) canpass an identifier (e.g., via near field communication, a camera, Wi-Ficommunication, BLUETOOTH® communication, text, e-mail, and/or in anyother suitable manner) from the first set, second set, and/or any othersuitable set of identifiers to one or more other devices to allow theusers of such other devices to carry the item for a portion of the trip.

Additionally, step 1208 shows that, in some embodiments, the method 1200optionally includes associating an identifier that coordinates with thefirst set of identifiers (and/or another applicable set) with the item(e.g., a package and/or any other suitable good and/or service) that isbeing transported as part of the first transaction. In this regard, thecoordinating identifier can be associated with the item in any suitablemanner, including, without limitation, be being printed on the item,being included on a sticker that is attached to the item, being printedon a receipt and/or other object associated with the item, being shownon a display associated with the item, being presented through a speakerassociated with the item, by being locatable through the use of a code(e.g., a QR code, bar code, numeric code, alphanumeric code, and/or anyother suitable code) that is associated with the item, by beinglocatable by scanning an RF ID associated with the item, and/or in anyother suitable manner. Accordingly, in some embodiments, not only canparties identify other parties in a transaction by matching theiridentifiers (e.g., manually and/or via their devices), but in someembodiments, one or more parties can identify an item associated with atransaction by matching an identifier associated with such item with oneor more identifiers provided by the parties' devices.

Continuing on with the method 1200, steps 1210 through 1214 show that,in some embodiments, the second device, one or more other devices thatreceive an identifier from the second device, and/or any other deviceparticipating in the first transaction can also participate in one ormore other transactions. For instance, while the user of the seconddevice (e.g., a deliverer) can enter into a first transaction to take anitem from the user of the first device to the user of a third device,the user of the second device can further enter into one or more othertransactions, including, without limitation, a transaction to deliver anitem from a fourth party to a fifth party.

At step 1216, FIG. 12B shows that some embodiments of the method 1200further comprise using a processor of the computer system 385 and/or aprocessor of one or more devices in a transaction to track the locationof the various devices in the transaction with respect to each otherand/or one or more devices that are part of another transaction. In thismanner, the described systems and methods can perform a variety offunctions, including, but not limited to, ensuring (e.g., as shown atstep 1218) that identifiers from one transaction are readilydistinguishable from the identifiers of one or more other transactions(e.g., where devices from the various transactions come or may come intoproximity with each other and/or otherwise), modifying one or moreidentifiers in a set of identifiers as devices in the same transactioncome into proximity with each other, providing one or more proposedroutes between various devices in a transaction, and/or any othersuitable function. Also, while FIG. 12B shows the method 1200 ends atstep 1220, the method can be repeated and/or modified in any suitablemanner.

With reference now to ticket purchases, the described systems andmethods can be used in any suitable manner to improve ticket salestechniques. Indeed, under some current techniques for purchasingtickets, after a person purchases tickets over the phone, online, etc.,someone has to go and pick such tickets up (e.g., at will call orelsewhere). That said, under some embodiments, the described systems andmethods (as shown by method 1300 in FIG. 13), allow a user to purchasetickets (e.g., on a mobile app, website, and/or other applicationconfigured to provide the described systems and methods; over the phone;via e-mail; via text; and/or in any other suitable manner (e.g., asshown at step 1302 in FIG. 13)).

As shown at step 1304, the method 1300 continues as an identifier isassigned to the transaction (e.g., to the customer's cellphone and/orother computer device). In this regard, the identifier can be provided adevice in the transaction (e.g., the ticket purchaser's phone orotherwise) at any suitable time and in any suitable manner, including,without limitation, at the time an order is placed, at the time ticketsare purchased, as the device comes into proximity with another device inthe transaction, and/or at any other suitable time. In some embodiments,however, the identifier is assigned to a transaction at the time ticketsare purchased.

At step 1306, FIG. 13 shows that the ticket purchaser (and/or any otherapplicable party) can optionally pass the tickets to one or more otherdevices (or people) in any suitable manner, including, withoutlimitation, via near field communications, a text, an e-mail, and/or inany other suitable manner. Thus, in some embodiments, an identifierassigned to a transaction can be passed from one person to another, muchthe same way that physical tickets can be passed. That said, although insome embodiments, as a first party passes one or more identifiers (e.g.,serving as tickets) to another party, the first party relinquishes theidentifier(s) (and/or tickets), in some other embodiments, as a firstparty passes the identifier(s) to one or more other parties, the firstparty (and/or one or more subsequent passing parties) continues to haveaccess to the identifier(s) on the first party's (or another applicableparty's) device or otherwise.

At step 1308, FIG. 13 shows that, in some embodiments, the method 1300continues as a party with the identifier uses the identifier to completeat least a portion of the transaction (e.g., using the identifier as aticket, in accordance with the method 800 of FIG. 8, and/or otherwise).While this can be done in any suitable manner, in some embodiments, theparty who is using the identifier as a ticket compares the identifierwith the identifier of another party (e.g., staff at an event) having acoordinating identifier. Thus, in some non-limiting embodiments, thedescribed systems and methods can provide a simple way to purchase andor use tickets, while being able to electronically track and/or passsuch tickets.

With reference now to concessions, the described systems and methods canbe used in the field of concessions in any suitable manner. In thisregard, FIG. 14A illustrates one representative embodiment of a methodfor using the described systems and methods to allow one or more patrons(and/or any other suitable customer) to purchase one or more items(and/or services) from one or more providers (e.g., concessions stands)and to have the items (and/or services) delivered to the patron by oneor more servers, runners, and/or other parties; hereinafter server orservers) in a way that the applicable patron(s) and server(s) canidentify each other through the use of coordinating identifiers.

While the method 1400 of FIG. 14A can proceed in any suitable manner,step 1402 shows that, in some embodiments, a transaction begins as oneor more patrons are allowed to make a purchase. In this regard, thepurchase can be made in any suitable manner, including, withoutlimitation, through a website, a mobile app, and/or any otherapplication that provides at least some of the described systems andmethods; by making a purchase in person (e.g., making a purchase andthen leaving the point of sale); by paying through the patron's computerdevice; by making one or more orders through the patron's device; bypaying in person (e.g., at the time the server delivers the desiredgoods and/or services), by paying at the time of making an order; and/orin any other suitable manner.

Indeed, in some embodiments, a patron is able to purchase one or moregoods and/or services directly through an app that functions inaccordance with at least some of the described systems and methods.Additionally, while in some embodiments, a patron is only able to usethe described systems and methods to make a purchase from a singleconcession stand (and/or other provider of goods or services) at a time,in some other embodiments, a patron is able to use the described systemsand methods to make one or more purchases from multiple providers,simultaneously or otherwise. By way of non-limiting example, in someembodiments, a patron can purchase one item (e.g., nachos) from a firstconcession stand, another item (e.g., a hotdog) from another stand, andany other number of items from any other number of providers.

At step 1404, FIG. 14A shows that some embodiments of the method 1400proceed as one or more servers are linked, assigned to, and/or areotherwise associated with the transaction and/or the patron. In thisregard, the servers can be linked with a transaction in any suitablemanner, including, without limitation, by being selected based onproximity to a provider and/or a patron (e.g., as determined by thelocation of server's computer device, the location of a the patron'sdevice, and/or preset location of the provider and/or patron), based ona server's affiliation with a provider providing the patron's selectedservices, and/or in any other suitable manner. Indeed, in someembodiments, one or more servers at or in proximity to an event can usethe described systems and methods to indicate that they are ready toprovide a service, and the described systems and methods can select suchservers in the manner determined to be most-efficient and/or in anyother suitable manner.

At step 1406, FIG. 14A shows that some embodiments of the method 1400include providing one or more patrons, providers, and/or servers thatbelong to a transaction with coordinating identifiers. Additionally, atstep 1408, FIG. 14A shows that some embodiments of the method 1400include tracking the location of one or more parties to the transaction(e.g., via GPS coordinates of a phone and/or other computer device ofone or more parties, multilateration, localization, information providedby a user, and/or in any other suitable manner). Indeed, in someembodiments, the described systems and methods are configured to provideone or more parties to the transaction with a map showing the positionof (and/or a proposed route to) one or more parties to the transaction.In one non-limiting example, the computer devices (e.g., devices 365 and375) of one or more patrons in a transaction show the locations (in nearreal-time and/or otherwise) of one or more servers (and/or vice versa)in one or more applicable transactions.

As shown at step 1410, in some embodiments of the described method 1400,one or more parties to a transaction receive an estimated time (and/orupdated estimates) indicating an estimated time until parties to atransaction meet (e.g., the server comes to the patron, the patron comesto the server, the patron comes to the provider, etc.). Indeed, in somenon-limiting embodiments, the described systems and methods are furtherconfigured to automatically update coordinating identifiers based on theproximity of one or more parties to a transaction (e.g., as discussedabove with respect to FIG. 6).

At step 1412, FIG. 14A shows that some embodiments of the describedmethod 1400 continue as two or more parties to a transaction are able toconfirm that the applicable parties have actually met and/or that atleast a portion of the transaction is complete. In this regard, one ormore portions of a transaction can be confirmed to be complete in anysuitable manner, including, without limitation, by determining thatcomputer devices of two or more parties to a transaction are within acertain proximity of each other (e.g., for any time and/or a set periodof time), by having one or more parties provide input to a computerdevice indicating that at least a portion of the transaction is complete(e.g., by tapping a visually perceptible identifier on a computerdevice, providing a signature through a computer device, swiping acredit card, making a payment, and/or in any other suitable manner), byhaving the applicable devices communicate with each other to confirm atransaction (e.g., via near field communications, wirelessly, and/or inany other suitable manner), and/or in any other suitable manner. Indeed,in some embodiments, two or more parties to a transaction simply hold uptheir devices, displaying coordinating identifiers, such that theparties to the transaction are able to readily match (e.g., visuallyand/or otherwise) the coordinating identifiers.

The method 1400 shown in FIG. 14A (and/or in any other applicablemethods) can be structured in any suitable manner. Indeed, in someembodiments (and as shown in section A of FIG. 14B) each transactioncomprises a coordinating identifier 1414 that is provided to a server(shown as the square labeled 1416), a patron (shown as the circlelabeled 1418), and/or a provider (not shown). Thus, in some suchembodiments, the server and the patron in a transaction can readilyidentify each other by showing their identifiers to each other andmatching their coordinating identifiers.

Moreover, in accordance with some embodiments, the described systems areconfigured to ensure that an identifier used for a particulartransaction is unique to that transaction, at least within a certainlocation (e.g., as discussed above with respect to FIG. 7). Thus, inFIG. 14B, section A, which depicts a first location (e.g., a firstvenue, a portion of the first venue, and/or any other suitable location)shows an embodiment with two transactions (one with a plus-symbol-shapedidentifier and another with a triangular identifier) that each comprisesa server 1416 and a patron, and wherein the respective server and patronfor each of the transactions have identifiers that are unique to theirtransaction (at least in the first location).

In contrast, Section B in FIG. 14B, which depicts a second location(e.g., a second venue, a portion of the second venue, and/or any othersuitable location) shows that, in some embodiments, one or more patrons1422 (or 1432) enter into a transaction, one or more servers 1420 (or1430), and/or providers (not shown); with each of the two transactionscomprising an identifier 1414 that is unique to the respectivetransactions (at least in the second location). Specifically, Section Bof FIG. 14B shows an embodiment in which a first transaction (as denotedby the triangular identifiers 1414) comprises a first sever 1420 who isassigned to serve (e.g., provide popcorn and/or any other suitable goodor service to) multiple patrons 1422 having a coordinating triangularidentifier 1414. Additionally, Section B of FIG. 14B shows an embodimentin which a second transaction (as denoted by the plus-symbol-shapedidentifiers 1414) comprises a second sever 1430 who is assigned to serve(e.g., provide drinks and/or any other suitable good or service to)multiple patrons 1432 having a coordinating triangular identifier 1414.

FIG. 14C further shows that, in some embodiments, one or more patronscan enter into a single transaction with one or more servers and/orproviders (not shown), with all members of the transaction havingcoordinating symbols. Specifically, FIG. 14C shows that, in someembodiments, a first patron 1440 can enter into a first transaction withmultiple servers 1442. For instance, the first patron may order fromseveral providers/servers in a single transaction (e.g., with one serverbringing nachos, another server bring a drink, another server bringingice cream, and another server bringing souvenir to the patron).Additionally, FIG. 14C shows that, in some embodiments, the identifiers(e.g., the triangular identifiers) for the first patron 1440 are uniqueto the first transaction (or are at least unique for a specificlocation), while other transactions in proximity to the first havediffering identifiers (e.g., as shown by the star-shaped andplus-symbol-shaped identifiers in FIG. 14C.

With reference now to queue management, the described systems andmethods can be used to manage a queue (e.g., in a restaurant and/or anyother suitable eatery, the DMV, a doctor's office, and/or any othersuitable location or circumstance) in any suitable manner. Indeed, FIG.15, at step 1502, shows that some embodiments include allowing one ormore people to enter into a transaction involving a queue (i.e., avirtual and/or physical queue). In this regard, such people can enterinto a queue in any suitable manner, including, without limitation, byvisiting an establishment, a teller, a cashier, a person, and/or othersuitable location in person; by entering into the queue online; bysending a text that places such people into the queue; by entering intothe queue through an application (e.g., any suitable app, including, butnot limited to, an app and/or website that functions in accordance withat least some of the described systems and methods); by entering intothe queue over the telephone; by sending a fax that is used to place aperson in the queue; and/or in any other suitable manner.

Continuing with the method 1500, step 1504 shows that, in someembodiments, the method continues as one or more parties to thetransaction (e.g., the person waiting in the queue and the person(and/or device) attending to people in the queue) receive coordinatingidentifiers. In this regard, the parties can receive the identifiers atany suitable time, including, without limitation, when it's a partiesturn in the queue, when the party enters into the queue, when two ormore parties in the transaction come within a set proximity of eachother, when requested by such party, after waiting in the queue for aspecific period of time, after arriving in a certain position in thequeue, and/or at any other suitable time.

Indeed, in some embodiments, a person receives a coordinating identifier(e.g., via that person's computer device 365) when that person entersinto the transaction (and/or the queue). In some such embodiments, whena party to the transaction comes to his or her turn in the queue, thecoordinating identifier provided on that party's computer device (and/orthe computer device of one or more other parties to the transaction) ismodified (e.g., one or more of the coordinating identifiers in thetransaction are changed, flash, display a message in association withthe identifier, and/or the identifier is otherwise modified and/orreplaced to indicate that a party's turn has arrived and/or is gettingcloser) and/or the person is otherwise notified (e.g., via text, email,SMS, vibration, and/or in any other suitable manner) that his or herturn has arrived and/or is approaching. In some other embodiments,however, a party to a transaction receives a coordinating identifierwhen his or her turn in the queue arrives.

At step 1506, FIG. 15 shows that some embodiments of the method 1500continue as one or more parties to the transaction identify each otherand/or otherwise confirm that at least a portion of the transaction iscomplete. In this regard, the transaction (or a portion thereof) can beconfirmed in any suitable manner. Indeed, in some embodiments, two ormore parties to a transaction (e.g., a patron and a maître d') are ableto compare coordinating identifiers to determine that the proper party'sturn has arrived (e.g., to be seated, to be serviced, to get on a ride,to enter an establishment, to enter an office, and/or to otherwisereceive goods and/or services).

In still other embodiments, however, a transaction (or a portionthereof) is confirmed by determining that computer devices of two ormore parties to a transaction and with coordinating identifiers arewithin a certain proximity of each other (e.g., for any time and/or aset period of time), by having one or more parties provide input to acomputer device indicating that at least a portion of the transaction iscomplete (e.g., by tapping a visually perceptible identifier on acomputer device, providing a signature through a computer device, and/orin any other suitable manner), by having the applicable devicescommunicate with each other to confirm a transaction (e.g., via nearfield communications, wirelessly, and/or in any other suitable manner),and/or in any other suitable manner.

As previously mentioned, each of the described methods can be modifiedin any suitable manner. By way of non-limiting illustration, the methodsshown in FIGS. 10, 11, and 13-15 can be modified such that one or moreidentifiers can be: passed from one party in a transaction to anotherparty (e.g., as discussed above with respect to FIGS. 11 and/or 12 orotherwise); modified as a distance between two or more parties in atransaction decreases and/or increases (e.g., as discussed above withrespect to FIG. 6 and/or otherwise); modified when one or more othermodification factors are met; displayed for the parties in a transactionthat are closest to each other (e.g., as discussed above with respect toFIGS. 7 and/or 8 or otherwise); displayed for the party and/or partiesthat are next in a queue and/or approaching a specific position in aqueue (e.g., as discussed above with respect to FIG. 8 or otherwise);and/or otherwise modified in any suitable manner.

As another example of a suitable modification, in some embodiments, anyof the described systems and methods is modified to include anidentifier that is associated with an item (e.g., one or more goodsand/or services). In some such embodiments, when a patron purchases anitem, an identifier (e.g., a non-numeric identifier, a non-customer nameidentifier, a symbol, an icon, and/or any other suitable identifier) isprovided to the patron (e.g., on a receipt, on a document separate froma receipt, on the user's device, and/or in any other suitable manner).For instance, in some embodiments in which a patron orders over thepatron's computer device, a coordinating identifier is also provided tothe patron through the patron's device (e.g., phone). In some otherinstances, when the patron purchases, orders, and/or otherwise entersinto a transaction for an item, the patron receives a receipt, a slip ofpaper, and/or any other suitable material carrying the identifier.

In the aforementioned example, an item can be associated with acoordinating identifier in any suitable manner. For instance, a stickercomprising the identifier can be stuck on the item, a receipt or otherslip of paper comprising the identifier can be placed on or be otherwiseassociated with the item, a display can show the identifier when theitem is available, and/or the identifier can otherwise be associatedwith the item. Indeed, in some embodiments, after a patron has orderedand item and received an identifier (e.g., a symbol on a receipt, asymbol and/or sound on an electronic device, etc.), the patron cancompare that identifier against the identifier associated with the itemto readily identify that the item pertains to that patron. For instance,where a patron orders food and the food all orders are set in one placewhen they are done and ready for pickup, the patron can readily look atthe identifiers on some or all of the food products and compare thoseidentifiers against the identifier received by the patron (e.g., on areceipt, on the patron's phone, etc.) to identify the patron's orderwithout needing to touch other people's orders.

As still another example of a suitable modification, some embodiments ofthe described systems and methods are configured to send a message(e.g., via text, e-mail, phone call, fax, IR signal, Wi-Fi signal,website, and/or in any other suitable manner), indicating a statusand/or location of one or more devices in a transaction, indicating thatone or more devices in the transaction have come to a desired location,indicating that two or more devices in a transaction are within a setdistance from each other, indicating that a package associated with thetransaction has reached a certain location, and/or any other suitableinformation.

In addition to the aforementioned uses, the described systems andmethods can further be used to help individuals identify and verify eachother for home deliveries, dating (e.g., for blind dates, dates arrangedthrough a website and/or dating app, etc.), classified add purchases(e.g., as individual's who come together through an interaction thatbegan on Craig's List, Angie's List, the newspaper, and/or any othersuitable venue meet to make a purchase, close a deal, and/orprovide/receive goods and/or services), as parties meet to broker ticketsales (e.g., ticket resale), airport pick up, appointments (e.g., withsalesmen, repairmen, missionaries, recruiters, service providers, etc.),breaking groups of people into smaller groups, food delivery, escortingminors on trips (e.g., only placing the minor in the custody of a partythat shows a identifier corresponding with the identifier assigned tothe minor), and/or any other suitable circumstance in which at least oneparty wants to identify another party and/or location.

In some embodiments, the described systems and methods can further beused with any suitable service provider (e.g., with an auto mechanic, atthe hospital, at a doctor's clinic, at a dentist's office, at amasseuse's office, at a chiropractor's office, and/or at any othersuitable place where services are provided). By way of non-limitingexample, under some conventional methods for providing healthcare, apatient may regularly have to provide personal information (e.g., name,date of birth, etc.) as the patient receives medical treatment (e.g.,when checking in, when getting x-rayed, when getting a shot, whenreceiving a procedure, and/or at any other suitable time). In accordancewith some embodiments of the described systems and methods, however, apatient (and/or a device associated with the patient) is assigned one ormore identifiers. Under some such embodiments, instead of needing toprovide personal information verbally (e.g., where it may be overheardand possibly used in identify fraud), the patient and one or moreservice providers (or the service providers' electronic devices) may beprovided with coordinating identifiers, allowing the patient and theproviders to readily identify each other (e.g., by showing matchingidentifiers, via near field communications, by scanning each other's QRcodes, and/or in any other suitable manner.

In some such embodiments, an identifier associated with a patient mayfurther be passed and/or otherwise provided to one or more otherindividuals (e.g., service providers, visitors, and/or any othersuitable person or device associated with such a person). Thus, in somesuch embodiments, the described systems and methods can be used toreadily identify that the proper parties are present. Additionally, insome embodiments (as in any other method described herein), if a personwho has a non-coordinating identifier tries to match thenon-coordinating identifier with an identifier from another transaction,the described systems and methods optionally cause one or more devicesin the transaction (and/or the device(s) comprising the non-coordinatingidentifier) to make a sound, provide a visual display, vibrate, and/orotherwise indicate that the identifiers do not coordinate. In someembodiments, the described systems and methods are further configured tosend a message (e.g., via text, e-mail, near-field communications,Wi-Fi, cell signal, short wavelength transmission, IR transmission,and/or in any other suitable manner) to provide an alert (e.g., tosecurity, to the police, to a system configured to lock a portion of afacility down, and/or otherwise) that someone tried to matchnon-coordinating identifiers.

Although in some embodiments, a patient receives an identifier via anelectronic device (e.g., a phone, tablet, etc.), in some embodiments,the patient receives a sticker, a printout, a badge, a paper, a receipt,a ticket, and/or some other form of identifier or item comprising anidentifier that can be matched by a service provider (e.g., matchedvisually, matched by scanning, matched by symbol and/or visualidentification technology, and/or in any other suitable manner). Indeed,in some embodiments, a patient is given a sticker and/or otheridentifier that is configured to be placed on a portion of the patient'sbody to be treated (e.g., operated on and/or otherwise examined ortreated) and a service provider can confirm the matching identifier(e.g., by comparing the symbol on the sticker with a symbol on anelectronic device and/or in any other suitable manner).

Accordingly, some embodiments of the described systems and methods areconfigured to: provide coordinating identifiers that are unique for agiven location (e.g., to prevent possible confusion and belief that oneor more third parties are actually part of a transaction); help partiesto a transaction readily and confidently identify each other; reduce theneed for additional equipment and/or materials (e.g., restaurant pagers;restaurant buzzers; tickets; printed, non-digital signs displaying thename of an intended party; and/or other materials); save time inidentifying parties; help parties to a transaction to properly identifyeach other in the dark; help one or more parties to a transaction toreadily pick another party to the transaction out of a crowd; and/or tootherwise reduce and/or remove shortcomings associated with someconventional methods for identifying parties to a transaction.Additionally, as some embodiments of the described system and method areconfigured to allow provide at least two-party validation such that bothparties can confidently identify the other.

Thus, as discussed herein, the present invention relates to systems andmethods for identifying parties through the use of one or morecorresponding, computer-coordinated identifiers. In particular, someembodiments of the present invention relate to systems and methods forusing a server or other computer system to provide (wirelessly orotherwise) computer-coordinated perceptible identifiers (such as one ormore images, light emissions, sounds, touch-perceptible identifiers,and/or other suitable identifiers) to two or more computer devices, withthe identifiers received by each of the devices coordinating with eachother to allow users of such devices to readily match the identifiersand to thereby identify each other. In some embodiments, the describedsystems and methods automatically ensure that coordinating identifiersreceived by computer devices participating in a first transaction do notcoordinate with an identifier provided to another device participatingin a second transaction when such other device is within a set proximityfrom one of more of the computer devices associated with the firsttransaction. Moreover, in some embodiments, the coordinating identifiersreceived by one or more of the computer devices participating in atransaction are configured to be modified when such devices come intoproximity with each other.

The present invention may be embodied in other specific forms withoutdeparting from its spirit or essential characteristics. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges that come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

What is claimed is:
 1. A computer program product for implementingwithin a computer system a method for dynamically identifying parties ofa first transaction through use of coordinating identifiers, thecomputer program product comprising: a computer-readable, non-transitorymedium for providing computer program code means utilized to implementthe method, wherein the computer program code means comprises executablecode for implementing steps for: identifying a first computer deviceconfigured to provide a first identifier that is humanly perceptible;identifying a second computer device configured to provide a secondidentifier that is humanly perceptible; providing the first identifierat the first computer device and the second identifier at the secondcomputer device, wherein the first and second identifiers correspondwith each other to provide multiple device, computer-coordinatedverification, and wherein as a first user of the first computer deviceand a second user of the second computer device come into proximity witheach other, the first identifier at the first computer device isconfigured to be readily humanly perceived, and matched with the secondidentifier, by the second user; receiving a request to modify the firstand second identifiers of the first transaction; communicating therequest within the computer system; and modifying the first and secondidentifiers of the transaction, wherein the first modified identifier isprovided at the first computer device and the second modified identifieris provided at the second computer device, wherein the first modifiedidentifier and the second modified identifier (i) are humanlyperceptible, (ii) correspond with each other to provide multiple device,computer-coordinated verification, and (iii) are distinguishable fromthe first and second identifiers of the transaction.
 2. The computerprogram product of claim 1, wherein the computer program product isconfigured to provide corresponding identifiers to computer devicespertaining to separate transactions, wherein the computer programproduct further comprises executable code for identifying a thirdcomputer device in a geographic location pertaining to at least one ofthe first computer device and the second computer device when the firstand second computer devices are participating in the first transactionand the third computer device is participating in a second transactionthat is separate from the first transaction, and automatically ensuringthat when the third computer device is in proximity with at least one ofthe first and second computer devices, at least one of: (i) the firstand second identifiers and (ii) the first modified and second modifiedidentifiers do not directly correspond with a third identifier that ishumanly perceptible and that is provided at the third computer device.3. The computer program product of claim 1, further comprisingexecutable code for changing the first and second modified identifierson the first and second computer devices with a fourth modifiedidentifier and a fifth modified identifier that are each humanlyperceptible, that correspond with each other, and that aredistinguishable from the first and second modified identifiers.
 4. Thecomputer program product of claim 1, further comprising executable codefor correlating a location of the first computer device with a locationof the second computer device, wherein the request is triggered based ona proximity between the first and second computer devices.
 5. Thecomputer program product of claim 1, further comprising executable codefor: receiving the request from at least one of the first computerdevice and the second computer device to modify the first and secondidentifiers, based on the request, dynamically replacing the first andsecond identifiers, on the first and second computer devices,respectively, to provide the first and second modified identifiers, andautomatically ensuring that the first and second modified identifiers donot correspond with a third identifier that is humanly perceptible andthat is provided to a third computer device when the third computerdevice is in proximity with at least one of the first computer deviceand the second computer device.
 6. The computer program product of claim1, further comprising executable code for: obtaining informationrelating to an identifier preference associated with at least one of thefirst and the second computer devices; and automatically determining acharacteristic of at least one of the first identifier, the secondidentifier, the first modified identifier, and the second modifiedidentifier based on the identifier preference.
 7. The computer programproduct of claim 1, further comprising executable code for using acamera of the first computer device to visually identify a vehicleassociated with the second computer device.
 8. The computer programproduct of claim 7, further comprising executable code for automaticallymodifying at least one of (i) the first identifier and (ii) the firstmodified identifier at the first computer device as a result of thevisual identification of the vehicle.
 9. The computer program product ofclaim 1, further comprising executable code for automatically trackingand recording a time during which the first computer device and thesecond computer device are within a set proximity from each other. 10.The computer program product of claim 1, further comprising executablecode for: enabling the first computer device to pass at least one of thefirst identifier and the first modified identifier to a third computerdevice, identifying the third computer device that has received the atleast one of the first identifier and the first modified identifier fromthe first computer device, and automatically modifying the at least oneof the first identifier and the first modified identifier received bythe third computer device when at least one of the second identifier andthe second modified identifier of the second computer device ismodified, such that newly modified humanly perceptible identifiersprovided at the second and third computer devices coordinate with eachother and are distinguishable from the first and second identifiers andfrom the first and second modified identifiers.
 11. A computer programproduct for implementing within a computer system a method fordynamically identifying parties of a transaction through use ofcorresponding identifiers, the computer program product comprising: acomputer-readable, non-transitory medium for providing computer programcode means utilized to implement the method, wherein the computerprogram code means comprises executable code for implementing steps for:identifying a first computer device configured to provide a firstidentifier that is humanly perceptible; identifying a second computerdevice configured to provide a second identifier that is humanlyperceptible; providing the first identifier at the first computer deviceand the second identifier at the second computer device, wherein thefirst and second identifiers correspond with each other to provide acomputer-coordinated verification; receiving a request to modify thefirst and second identifiers of the transaction; transmitting therequest within the computer system; and providing, in response to therequest, a first modified identifier at the first computer device and asecond modified identifier at the second computer device such that thefirst and second modified identifiers of the transaction (i) correspondwith each other, (ii) are readily distinguishable from the first andsecond identifiers, and (iii) are configured to be readily humanlyperceived, and to be matched by the user of the first computer device.12. The computer program product of claim 11, further comprisingexecutable code for identifying a third computer device in a geographiclocation pertaining to at least one of the first computer device and thesecond computer device, and automatically using device location toensure that at least one set of (i) the first and second identifiers and(ii) the first and second modified identifiers do not directlycorrespond with a third identifier that is humanly perceptible and thatis provided at the third computer device.
 13. The computer programproduct of claim 11, comprising executable code for: providing a thirdidentifier that is humanly perceptible at a third computer device,wherein the first identifier, the second identifier, and the thirdidentifier all correspond with each other to provide multiple device,computer-coordinated verification, and automatically modifying two ofthe first, second, and third identifiers to provide two of the firstmodified identifier, the second modified identifier, and a thirdmodified identifier, which are distinguishable from the first, second,and third identifiers, when one of the first, second, and thirdidentifiers is modified.
 14. The computer program product of claim 11,further comprising executable code for ensuring that the computer systemdoes not provide a third identifier that is humanly perceptible and thatcoordinates with at least one of the first identifier and the secondidentifier to a third computer device that is within a certain distancefrom the at least one of the first computer device and the secondcomputer device.
 15. The computer program product of claim 11, whereinthe first computer device comprises a peripheral device and wherein thefirst identifier is provided at the peripheral device.
 16. The computerprogram product of claim 11, further comprising executable code forcontrolling a light source of a vehicle carrying at least one of thefirst computer device and the second computer device.
 17. A method forproviding coordinating identifiers over a network to multiple remotecomputer devices of a transaction, the method comprising: providing aparty-identification application for use on a first computer device anda second computer device; providing a first identifier that is humanlyperceptible at the first computer device and a second identifier that ishumanly perceptible at the second computer device when the first andsecond computer devices are participating in a first transaction,wherein the first identifier and the second identifier coordinate witheach other, wherein as a first user of the first computer device and asecond user of the second computer device come into proximity with eachother, the first identifier on the first computer device is configuredto be readily humanly perceived, and matched with the second identifier,by the second user; providing a third identifier that is humanlyperceptible to a third computer device that is participating in a secondtransaction, wherein the second transaction is distinct from the firsttransaction; determining a location of at least one of the firstcomputer device and the second computer device; determining a locationof the third computer device; ensuring that the first identifier and thesecond identifier do not correspond with the third identifier providedto the third computer device when the third computer device is inproximity to the at least one of the first computer device and thesecond computer device; receiving a request to modify the first andsecond identifiers of the first transaction; communicating the request;and modifying the first identifier and the second identifier of thefirst transaction in response to the request, wherein the first modifiedidentifier is provided at the first computer device and the secondmodified identifier is provided at the second computer device, whereinthe first and second modified identifiers (i) are humanly perceptible,(ii) are distinguishable from the first, second, and third identifiers,and (iii) correspond with each other to provide multiple device,computer-coordinated verification.
 18. The method of claim 17, furthercomprising: tracking a location of the first computer device and alocation of the second computer device; and wherein the request tomodify the first and second identifiers of the first transaction occurswhen a distance between the first computer device and the secondcomputer device reaches a set distance.
 19. The method of claim 17,wherein the modifying the first identifier and the second identifier ofthe first transaction in response to the request comprises replacing thefirst and second identifiers with the first and second modifiedidentifiers, respectively.
 20. The method of claim 17, furthercomprising: checking a proposed route between the first computer deviceand the second computer device, and ensuring, based on a potentialdevice location of the third device and the proposed route between thefirst device and the second device, that the first identifier and thesecond identifier do not coordinate with the third identifier providedto the third computer device when the third computer device is inproximity to the proposed route between the first computer device andthe second computer device.